This article is for Tempo Data Center
\uD83D\uDCD8 Instructions
On Data Center, with Automation for Jira, we can set Tempo Account of child issue based from Epic’s Account.
-
Set up an automation rule under Project Settings > Project automation
-
Add the trigger for “Issue created”
-
Select the condition with “Related issues condition” for Epic and Exists
Epic exists -
Add the action “Edit issue” with copy Tempo Account from Epic issue
Tempo Account from Epic
-
Save and turn it on
-
Create a new issue in the project and select an Epic link where Tempo Account value has been set.
-
You can see that Tempo Account value has been inherited from Epic.
This rule works similar on both Cloud and Data Center.
\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