You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is there a way to automate epics so that if they do not have a parent initiative, they are automatically assigned? We will always only have one initiative per project, and want epics to be automatically assigned to that initiative in case that step is missed.
We have this so far, but we need a way to automate the initiative ID, rather than hard coding it like we have here, "CST-8"
Resources used so far:
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
Hi @Nikki Hylton - If you're looking to get the initiative dynamically, you could do something like this...
Just before your Edit Issues Action, add a Lookup Issues action
issueType = Initiative
For good measure, you probably want to make sure that there is only one Initiative so you could add an advanced condition of:
{{lookupIssues.size}}
Equals
1
Replace CST-8 in your Edit issues action with this:
{{lookupIssues}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mark Segall - thanks again for your help before! This worked perfectly within a project, but now we're trying to make a global rule across all projects. We have a global rule in place which is now searching for Initiative across all projects... so we'd like to modify it to lookup the Initiative in the same project where the issue (epic) is being created. Any ideas?
Thanks again,
Nikki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, following the same assumption that there is one and only one initiative per project, you would change your lookup issues action to this:
project = {{issue.project}} and issueType = Initiative
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe try this instead:
project = {{issue.project.key}} and issueType = Initiative
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does the single initiative for the project live within that project or in it's own project? Is there anything in the initiate that identify which project it belongs to? If the answer is yes to either of these questions you could use the lookup issues action to get the issue key for the initiative and then add it to the epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The single initiative lives within that project. Lookup function worked - thank you!!
Nikki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.