...
We assign time record data depending on the field type to avoid duplicate data in reports. If you use the Tempo Team custom field on an issue, Tempo prioritizes the Tempo Team assigned to the issue when grouping time records, worklogs, or plans in Logged and Planned Time Reports.
Tempo Team-related fields without assigning a Tempo Team to a Jira issue
We use the team that a team member has most recently joined for the following fields:
...
The Team Lead, Program, and Program Manager are then derived from the latest team association.
Tempo Team-related fields when assigning a Tempo Team to a Jira issue
If you add the Tempo Team to the Jira issue view as a custom field, we use that team assignment when assigning the time record data. This prioritization only applies when:
The user is part of the selected Tempo team.
The team member is active in the Tempo team.
For example, when a team member is part of multiple teams, Tempo assigns the time record data to the Tempo Team from the Jira issue.
However, if the team member is not a member of the Tempo Team assigned to the Jira issue AND has worked on the issue, the time record is assigned to the last team the team member joined.
Multi-value options in issue-related fields
...
To simplify the report view, reports containing multiple grouping levels do not display "empty" hierarchy levels.
The following example shows a report grouped by Epic/Issue/Sub-task/Worklog. No epic hierarchy level is shown for Issue PRO-11 since it isn’t linked to an epic. Also, there is no hierarchy level for Sub-tasks because the issues do not have any. This makes the report look tidier and easier to read.
When you group by Epic and then Issue, a No Issue item displays. This item collates any time spent on the parent issue, including no time spent.
...
You can group by Initiative or other parent issues beyond Epic (issue type hierarchy levels 1 and above) configured in your Jira instance. We support Jira Premium issue hierarchy levels and custom hierarchy naming in non-Jira Premium editions. These options are available in Logged and Planned Time Reports under Jira Fields.
...
Group by | What it does | Available report or timesheet |
|---|---|---|
Account | Groups data by Tempo accounts |
|
Account Category | Groups data by Tempo account category |
|
Account Contact | Groups data by Tempo account contact |
|
Account Lead | Groups data by the Tempo account's account lead |
|
Account Status | Groups data by Tempo account status |
|
Assignee | Groups data by the assignee |
|
Category Type | Groups data by Tempo account category type |
|
Component | Groups data by Jira components |
|
Custom Fields (single value) | Groups data by one of the following custom fieldsfield types:
|
|
Custom Fields (multiple value) | Groups data by the first value returned in one of the following custom field types:
|
|
Customer | Groups data by Customer |
|
Epic | Groups data by Jira epics |
|
Fix version | Groups data by the Jira fix version |
|
Issue | Groups data by Jira issues |
|
Issue Type | Groups data by Jira issue type |
|
Labels | Groups data by Jira label and the following additional fields:
|
|
Organizations | Groups by the Jira Service Management Organizations field. This field is found in the Custom Fields. |
|
Plan | Groups data by plans |
|
Priority | Groups data by priority |
|
Project | Groups data by Jira projects |
|
Program Manager | Groups data by program manager |
|
Programs | Groups data by Tempo Program |
|
Reporter | Groups data by who reported the issue |
|
Request Type | Groups by the Jira Service Management Request Type field. This field is found in the Custom Fields. |
|
Role | Groups data by Tempo team role |
|
Sprint | Groups data by sprint |
|
Status | Groups data by issue status |
|
Sub-task | Groups data by Jira sub-tasks |
|
Team | Groups data by Tempo teams |
|
Team Lead | Groups data by Tempo team lead |
|
User | Groups data by Jira user |
|
Work Attributes | Groups data by any work attribute type, such as:
|
|
Worklog | Groups data by worklogs (time records) |
|
...