Automation rule to use the parent link/summary after the parent was changed

Dave Furlani March 13, 2024

I am trying to create a rue that will notify people when tickets are removed from certain epics (by key words in the parent Summary).

I have created a rule triggered by changes to the the Parent field, however I am having no luck using .from or .fromString on issue.parent.

I've lost could of the permutations I've tried, but they include:

{{issue.parent.summary.fromString}} 
{{issue.parent.summary.from}}
{{issue.parent.from}}
{{#changelog.parent}}{{fromString}}{{/}}

I need to be able to get the Summary of the old parent as a smart value (or variable) so I can filter before sending comms, which will need to include the old and new parent's Summaries

Help

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 13, 2024

Hello @Dave Furlani 

That does not work because it is the Parent field itself that is changing, not the parent's Summary field. 

If your rule trigger is Field Value Changed and monitoring the Parent field then you can use the {{fieldChange}} smart value to get the before and after values of the field. The documentation for that smart value can be found here:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

However, that will be just the string value of the field, not a reference to the issue entity referenced by the field. You'll have to execute steps to actually get the previous Epic issue.

You might be able to use something like this to branch to the original parent epic issue and get the summary:

Screenshot 2024-03-13 at 11.28.41 PM.png

Note that if the content of your communications depends on both the original parent summary and the new parent summary, the steps related to examining those value and sending the message would need to occur within the branch. Branches and the steps within the branch run in parallel to steps that are at the same level where the branch split off, so steps added where the Add Component button is would be executing at the same time as the steps within the branch. Additionally a variable created within a branch will be unknown and undefined outside of that branch.

Alternately you might use the Lookup Issues action to retrieve the original parent Epic, and then reference the issue entity Summary using {{lookupIssues.first.Summary}}

I would recommend adding conditions also to ensure that the rule is triggered by a change on an issue type that may be a child of an Epic. The Parent field is also used in sub-tasks, and in Epics and issue hierarchy levels above Epic (if you have created those). So you can't assume that when this rule is triggered (as is) it was triggered by a change to a child of an Epic.

Let us know if you have additional questions.

Dave Furlani March 14, 2024

Thank you @Trudy Claspill , that is a nicer way to get the from parent key than {{#changelog.epic link}}{{fromString}}{{/}}

The first step is a filter that rules out sub-tasks, and projects that aren't of interest to us:

key = {{issue.key}} AND issuetype in standardIssueTypes() AND category = "System Layer"

 

I'll now work through the lookup approach to find the parent's parent to focus the actions on the initiative of interest.

Suggest an answer

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

Atlassian Community Events