nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Populate initiative details at Standard issuetype

Vishal Biyani_2pr07j

I have JIRA Cloud Premium plan and have defined issuetype = Initiative above Epic.

In Epics parent field we specify the Initiative#.

Now I want few fields on Initiative to be populated at StandardIssue Type level like Story and Task in custom field.

Using automation how can i accomplish this.

I tried

For Parent

store {{issue.parent}} in a variable. i get the correct Initiative Key

Now what rule should i write so that custom field in the issue that triggered the rule, can be updated with field values of initiative key obtained above?

Accepted answers

Trudy P Claspill

Hello @Vishal Biyani

Please show us the complete rule you have constructed so far.

All comments

Trudy P Claspill

Hello @Vishal Biyani

Please show us the complete rule you have constructed so far.

Trudy P Claspill

If the trigger issue is the Story, and you want to get data from the issue two levels up (Story is child of Epic, which is child of Initiative), you can get that data without a For Each branch.

{{triggerIssue}} references the trigger issue - the Story.

{{triggerIssue.parent}} will reference the parent Epic of the Story.

{{triggerIssue.parent.parent}} will reference the parent Initiative of the parent Epic of the Story.

Tack onto that smart value the field name for the data you want from the Initiative; i.e. {{triggerIssue.parent.parent.status}}

Vishal Biyani_2pr07j

@Trudy P Claspill

This is very helpful and simplifies my logic.

I recently added the custom field (custom_10300). This field is available at all issuetypes. I want to populate this field on issue creation up to epic level, if it is empty.

So, if the trigger is sub-task, i can check for parent and update the field at story/task level. How do i check for Epic is not clear to me?

JQL: issuetype in subTaskIssueTypes()

if custom_10300 is empty

then edit (Advanced)

{
"fields": {
"custom_10300": "{{ triggerIssue.parent.parent.key }}|{{ triggerIssue.parent.parent.customfield_10182 }}|{{ triggerIssue.parent.parent.customfield_10183 }}|{{ triggerIssue.parent.parent.customfield_10184}}"
}
}

For Parent (Story/Task)

if custom_10300 is empty

then edit (Advanced)

{
"fields": {
"custom_10300": "{{ triggerIssue.parent.parent.parent.key }}|{{ triggerIssue.parent.parent.parent.customfield_10182 }}|{{ triggerIssue.parent.parent.parent.customfield_10183 }}|{{ triggerIssue.parent.parent.parent.customfield_10184}}"
}
}

How to go to epic level?

Trudy P Claspill

Hello @Vishal Biyani

I am slightly confused.

You original question was about bringing data from a higher level (Initiative) to a lower level (standard issues).

You new question seems to be about taking data from a lower level (sub-task) to a higher level (Epic).

Which scenario are you trying to address?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud