Hi :)
I hoping someone more skilled than me can help!
I've been trying (and failing!) to wrangle with Automations to populate a custom "Grandparent" field with the name/summary of the parent Initiative of a task.
Using previous posts in the Community, I've managed to populate the field with the Key of the initiative, however I can't figure out how to switch the key out for the summary (or use the key to lookup the summary, and then edit the field based on the lookup). This is the working flow to populate the Key;
I've attempted to switch out the word "Key" for "Summary" in the above flow, and also tried to add additional branches to lookup the key first and then lookup the summary based on the created variable, but "branching a branch" didn't seem to be possible. I feel like I'm working with about 5% of the knowledge I need to be able to make automations work, so I'm struggling to troubleshoot what I'm doing to know which bits should work and which is just JQL nonsense that I've made up!
Any and all help would be much appreciated! Thanks :)
-----------------
Ultimate Goal/Use Case Context
I'm trying to create a multi-layered set of boards within a single Jira project. One top-level kanban board which shows the overall progress of a portfolio of initiatives and a second/third/fourth etc. kanban board(s) which offer more conventional task/issue-level control of a selection of each of these initiatives. On the task-level boards, I need to be able to show the parent initiative on the cards (in a similar fashion to how Epic is normally shown) so that users are able to recognise which tasks are associated with each Initiative but still be able to have all of their work visible in one board.
I do something similar, you don't need the lookup issues, create variable or even the branching conditions:
Keep your trigger and IF statements but move your edit condition to directly after the IF and change it to
Grandparent
=
{{issue.parent.parent.summary}}
This worked like a dream! Amazing! Thanks so much :)
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.