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; } } }

Copy a field value from Initiative to Epic when Epic ticket is parent linked to Initiative

Kay_4fx3vl

Hello Community,

Can you please advise how can I copy a field value from Initiative to Epic? Epic ticket is linked to Initiative through "parent link". I can do that with Epic to Story without any issues, using the Copy Value From Other Copy Value From Other Field Post-Function and Automation Rule, but when it comes to Initiative issuetype it doesn't do anything. Any suggestion is highly appreciated. Thank you .

Kay,

Comments

Earl McCutcheon

Hello @Kay ,

There are some fields that are baked into the base functionality of Portfolio directly to alter the Base Jira behavior and do not live as a traditional field types for Jira, as they have additional functionality outside the traditional field types and exist in different locations of the database to complete the special functions. The "Parent Link" field is one of these Special Portfolio field types used to map a standard issue type to the higher hierarchy levels.

Because of this the "Parent Link" field is not a searchable field by many add-ons including automation for Jira, so you won't be able to do this like you described.

The Functionality needed to use the field in this manner is being tracked in the following Feature Request in both Jira Cloud and Server respectively, I am adding both incase anyone else runs into this thread looking for a solution on the alternate platform:

Regards,
Earl

Hristina Valcheva

Hello @Kay

I'm looking for an Automation rule which can copy a value from a cascading type field of an Epic to its child tasks (issuetype Story), can you please share your code for this with me?
Thank you in advance!

Kind Regards

Hrisi

Lisa Schaffer

Hi there,

You can use this:

{
"fields": {
"Client": {
"value": "{{issue.Client.value}}",
"child": {
"value": "{{issue.Client.child.value}}"
}
}
}

--------

"Client" = Name of Field

Client.value = first value in cascade drop down menu

Client.child.value = second drop down menu value

--------

Also check out Ravi's video here: https://www.ravisagar.in/videos/jira-cloud-automation-copy-cascading-select-list-sub-task

It's for a sub-task but you can adjust for copying from an Epic.

Good Luck!

Welcome!

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

Quick Links

Find more posts tagged with

advanced-roadmaps

automation