This article is for Tempo for Cloud.
To set Tempo Team on the child issue of a Parent, with Jira Automation, this can be done with a few steps. In this tutorial, we will set Tempo Team based on the Parent issue’s team for the child issue created.
\uD83D\uDCD8 Instructions
Set Tempo Team from Parent for new child issue by Project
-
Set up an automation rule under Projects > Settings > Automation
-
Trigger of the rule choose “Issue created”
-
Add a new condition > Related issues condition
-
Select “Parent” for Related issues, “Exists” for Condition and Rule restricted to projects for your projects
valid parent issue link
-
Since Tempo Team is not an available field in Jira automation (unlike Tempo Account), you need to get it as a Jira custom field from the Parent issue.
-
Get the issue key of the Parent issue into a variable {{ParentKey}}
get parent issue key in a variable
-
Send web request to get Parent issue details from variable {{ParentKey}}
get parent issue details
-
Create a variable to store the Team ID from the Parent issue (you should have your own Jira customfield_##### field number)
store parent team ID in a variable
-
Update the child issue’s Team ID from Parent
Update team ID on child issue
-
Save and publish the automation
-
Create a new child issue in the Parent issue of the project(s). You should see Tempo Team value has been inherited from the Parent.
Please make sure the Team is set on the Parent issue and the Team is linked to the project.
Modify the conditions can setup for other parent issues too.
Tempo Team automatically inherit from Parent.
\uD83D\uDCCB Related articles
- Hide the Tempo panel on the Jira issue view with ScriptRunner
- Set Tempo Team from Parent
- Best Practices for Tempo Cloud REST API
- Migrating Tempo data between Jira hosting environments
- Configuring Expense & Revenue Categories in Tempo
- Set Tempo Account from Epic
- Tempo is aligning with Atlassian to comply with GDPR standards
- Convert time data in Excel export to Jira format
- Handling of mixed cost rates
- Continuous logging work with a single check mark to "Log another"
- Timesheet approval "auto-approve" script on Data Center
- Automation Paused
- Estimated cost calculations
- Advanced SAFe (Scaled Agile Framework) with Structure
- How to install Tempo Server 10.18.x from 10.19.x and 10.20.x
- Log automated work on a Jira transition
- Tempo Timesheets - FAQs
- Tempo Planner - FAQs
- Create a Tempo plan on user assignment
- Convert time data in Excel export to Jira format
- Automation Paused
- Changes made to the Jira SPI in Tempo Timesheets version 10.19.0, Tempo Planner 7.19.0 and Tempo Budgets 13.19.0
- Migrate the Tempo Account Custom Field from Data Center to Cloud