This idea has been merged into another idea. To comment or vote on this idea, please visit T-I-364 Allow all tickets within an Epic to inherit the Epic's Account.
We generally have Epics that have the Account set correctly. Users then create regular Tasks within the Epic.
We would like for Tasks to have the same Account as their parent Epic by default. Rather than having the default be 'None', and then risk the user setting it incorrectly.
In fact, the Team field behaves exactly how we want: it inherits the Epic's value by default (see screenshot). It is just the Account field that doesn't.
Jeff Turner
| Tempo Products | Tempo Timesheets |
| Tempo Platform | On-Premise |
Well wouldn't it even make sense to set the account per project at highest level optionally?
Attachments Open full size
To refine this request: internally, the 'Team' field has the value 'INHERIT', which means "Whatever the Epic's value is". That is exactly the behaviour we'd like for Account: the ability to set its value to "Whatever the Epic's is".
Attachments Open full size
Hej :) how can I vote for this improvement? It is quite important to us especially after moving from Server to Cloud version. Best, Elisa
Attachments Open full size
Hi Jeff,
Thanks for the feedback! Yes this is something we are interested in improving, and I'm looking into if there are any technical obstacles, so at the moment I don't have an ETA for you. In the meantime, we have created, in collaboration with Adaptavist, a script that does exactly this which you may be interested in exploring. Of course this depends on you having Scriptrunner installed, so this solution may not work for you.
https://library.adaptavist.com/entity/select-tempo-account-automatically-at-issue-creation
Kind Regards,
Hlynur Johnsen
Group Product Manager - Tempo for Jira
Attachments Open full size