Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

With the recent change from Epic Link to Parent how to I automate based on Parent value?

Scott Howard December 19, 2023

With the recent change from 'Epic Link' to 'Parent' how might I automate the creation of a sub-task based on text within the 'Parent' name? I cannot see the 'Parent' field available when creating an Issue fields condition though I do see 'Epic Name'. 

1 answer

1 accepted

2 votes
Answer accepted
Trudy Claspill
Community Champion
December 19, 2023

Hello @Scott Howard 

The Parent field doesn't contain text. It contains an issue key.

If you need to set a condition based on the text of the associated issue, you'll have to reference the Summary field of that issue.

Can you provide more information about your scenario? 

Scott Howard December 19, 2023

Hi Trudy -

Thanks for the quick reply. When an issue is created or changed I would like to check the Parent/Epic Link and based on a specific value for that Parent/Epic Link I would like to conditionally create a sub-task reminding developers to perform a specific task.

In my case the Epic Link was called 'Security Vulnerability' and when changed to the Parent is now called 'PT-14636 Security Vulnerability' so my automation is constructed as follows: 

  1. When Value changes for Parent (I've also tried Parent Link and Epic Name)
  2. And Issue Type is Task, Story or Bug
  3. And Epic Name contains 'Security Vulnerability' (can't find any reference to Parent here other than 'Parent of sub-task')
  4. Then Create a new Sub-Task.

Thanks for your help!

Trudy Claspill
Community Champion
December 19, 2023

Hello Scott,

You can reference fields in an issue's Parent issue using the smart value:

{{issue.parent.<parentFieldName>}}

For example, if you wanted to look at the Summary field for the parent issue you would use:

{{issue.parent.summary}}

Note that Epic Name was applicable only to Epics in Company Managed projects. Atlassian is in the process of deprecating that field in favor of using just the Summary field in Epics (as is currently the case for Epics in Team Managed projects). So you may want to use the Summary field in your comparison rather then Epic Name.

A rule like this should do the trick.

Screenshot 2023-12-19 at 3.41.55 PM.png

Like Bill Sheboy likes this
Scott Howard December 20, 2023

That did the trick! Thanks so much Trudy!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events