How to differentiate my worklogs based on a project?
The simple way to do it is to create multiple worklog sources for different projects and define a different color for each worklog source. Please refer to the page to find out more about worklog source configuration.
Should you prefer to have just one worklog source and worklog entries to be in different colors depending on a certain condition, you can create and apply the conditional colors.
The conditional colors can be created and saved, in a source configuration.
In case you want the worklog events to differ in color based on a project, you would have to edit the worklog source configuration and add the conditional colors based on the filed “Project“.
Please take a look below:
We miss the old feature "Spent Vs Planned" report. How do we recreate it in the new app version?
To generate a report "Spent Vs Planned", first, please make sure that your calendar contains the required sources: Worklogs and Planning. Please refer to the Event Sources Tab of your calendar to verify this. Second, in Reports mode, configure the fields for reporting as Day and Event Source.
You might want to add other fields as well, depending on your business needs.
Then, add the fields Day and Event Source to the field sorting and tick the checkboxes “Group by“ next to them, as shown below:
You might want to add other fields to sorting and grouping. Again, it depends on your business needs.
Finally, generate a report. Your report might look similar to the one below:
We would like to generate a report for former users
For those who use cloud Jira this can be done the next way:
as admin, create a special group for inactive users
add inactive users to the group
create a worklog source configured for the group of inactive users
generate a report based on the source
For server Jira users, it is recommended to make users inactive rather than remove them from Jira in order to save their connection to the worklogs. In such a case, the worklog history is saved and the reports can be easily generated.
In case a user is removed from Jira, his or her worklog history is lost. In order to see the worklogs that belong to removed users you would have to create a worklog source with the configuration: Jira filter “All issues“ and user option “All“. As result, all worklogs will be shown for former users. Please see below:
In my report, I want to see the total work logged for the parent task and its sub-tasks
We’ve prepared a special field for that, aggregated Parent (“Σ Parent“). Please see below:
In my report, I want to see the total work logged for the epic task and its tasks
We’ve prepared a special field for that too, aggregated Epic (“Σ Epic“). Please see below:
In my report, I want to see the epic name in case there is an epic link for a task
Please use the field aggregated Epic Name (“Σ Epic Name“) as shown below:
The generated report is not being downloaded
One of the reasons why the generated report is not being downloaded is that multiple downloads are blocked. Please check your browser if this is the case.
Manage multiple downloads if needed.
The report is being generated in days and I prefer it to be generated in hours
You can change the time units for reports, by clicking next to Total, on the left panel:
I want to see the planning events created by others
In order to see the planning made by others, you may either
create a Planning calendar
in your calendar, that contains a planning source, grant the visibility and event editing permissions to other users
When using the first option, the planning calendar can be created as a public calendar so each user has access to it. The planning source shall be added to it. Thus, each user will be able to create a planning event based on the source.
In addition, should you prefer to work only with your calendar, without accessing the Planning calendar, you can add iCalendar source to your own calendar. Prior to it, you would have to create the export for the Planning calendar. Then, in your calendar configuration, add iCalendar source, using the generated URL for the Planning calendar export.
Once the iCalendar source is added to your calendar configuration, you will see the planning events made in Planning calendar, in your own calendar. If needed you’ll be able to create worklogs based on imported events.
When using the second option, other users who are granted the visibility and event editing permissions shall be able to access your calendar and create events there.
In such case, you may want to create Team planning source, in your calendar configuration. Then, grant the required permissions to other users, assuming your calendar is not public. As result, the users who are granted the visibility and event editing permissions shall be able to create and edit planning events.
I want to see Logged vs Planned for each day
In order to see logged time versus planned time in daily total hours, you would have to do next:
Next to Total, on the left panel, tick the checkbox “Detailed“, as shown below
2. Make sure the first two enabled sources, on the left panel, are the sources you would like to compare in your daily detailed time
The sources to be compared don’t have to be the very first two sources in the list, on the left panel. They have to be the first two enabled. Please see another example below.
Why I don't see the created calendar, in a project context view?
Most likely, you don't see the created calendar, in a project context view, because it doesn't contain any sources associated with the given project.
The conditional color that includes the function “endOfWeek()“ is not working properly
You might experience the next issue when the configured conditional color that includes the function “endOfWeek()“ is not working correctly.
For instance, as an app user, in User settings, I’ve configured my week to start on Monday:
Then, in source configuration, I’ve configured the conditional color: Due date <= endOfWeek() → red.
Although, the configured conditional color is not applied to the event that is based on issue that has a due date that falls on Saturday of the current week.
The root cause of the issue is laying in Jira’s behavior as, in Jira, week starts on Sunday.