Does issue.epic.summary work for Tasks in Team Managed Software Projects?

[Rasneet Kanwar]

Hi, we've set up automation to copy Epic Summary into a custom text field "EN". The rule is working fine for the Company Managed projects but is returning "None" for the Team Manged Project for the Task type of Issues.... Here's what we are using:

1. When: Issue Created

2. If matches: Issue Type equals Subtask

2.1 Then: Edit issue fields - Set EN as {{issue.parent.epic.summary}} ---- Works fine on Company and Team Managed Projects.

3. Else - If matches: Issue Type is one of : Task, Bug, Story

3.1 Then: Edit issue fields - Set EN as {{issue.epic.summary}} ----- Works fine on Company Managed Projects but returns "None" for Team Managed Projects.

I have also tried to use parent instead of epic but that also returns "None". Please advise.

[Trudy Claspill · Accepted solution]

Hello @Rasneet Kanwar 

Welcome to the Atlassian community.

Are you trying to use a Global automation rule against both Company Managed and Team Managed projects?

Can you show us the Audit log information for this rule running against a Team Managed project where the Else-If condition is executed?

[Rasneet Kanwar]

Hi @Trudy Claspill 

Thanks for looking into my concern. Yes, it will be set to global automation but I am currently testing it on a Team Managed Project as it has already passed the Company Managed Project Testing. Please advise further.

Thanks, Rasneet

1. Audit Log Image

2. Context Fields Image from Task Issue RT-95

3. Image of Rule Details

[Trudy Claspill]

Can you add a Log action immediately before each Edit Issue action to print the content of your smart value into the Audit Log?

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action

Make each Log action content a bit unique so that we can tell which output is from which action.

[Rasneet Kanwar]

Thanks again... As suggested, here's an image of Audit Log with Log action. 

Regards, Rasneet

[Bill Sheboy]

Hi @Rasneet Kanwar 

Yes, and...to Trudy's suggestions:

I just tried this with a team-managed project and {{issue.parent.summary}} works as expected for the parent epic of a story/task/bug issue.

Please also post images of what you have in your Edit Issue actions to confirm your smart values.  Thanks!

Kind regards,
Bill

[Trudy Claspill]

I tried {{issue.epic.summary}} in a Team Managed project, using a project-specific rule and it also worked.

I think that the problem is actually that this is a Global rule, and the "EN" field in the Team Managed project may not be the same "EN" field that is used by Company Managed projects.

When you added the "EN" field to the Team Managed project did you create a new custom field in the project, or did you use the option to search for a field and then reuse the "EN" field that was defined for the Company Managed projects?

[Rasneet Kanwar]

Hi, thanks for working with me on this.

Its a very basic rule and process but seems like we've been unable to fetch the summary/key/custom field value for parent or epic in Team Managed Projects for Task Level Issues.  

Here's how we created the test Project and issues: Create New Project - Team Managed, Software Development; From Timeline, Create Epic; Create child issues under Epic; Create SubTask under Tasks. 

@Bill Sheboy here's an image of the Edit Issue for Task/Story/Bug

@Trudy Claspill We created a custom text field "EN" and used it in our Company Managed and Team Managed Projects. Therefore the EN field used is essentially the same in all projects. Also, since we've never got any error regarding the field, the issue seems to be more related to the Values associated with Epics. 

Please advise on how to refer to epic/parent summary without using the smart values {{issue.epic.summary}} or {{issue.parent.summary}}.

Thanks, Rasneet

[Bill Sheboy]

Ah, I just noticed the rule trigger is Issue Created...

That trigger can fire so fast that the issue data is not yet available.  This can cause conditions, actions, and other things to work unexpectedly due to missing data.

The work-around for this is to always add a Re-fetch Issue action immediately after that type of trigger.  That will slow down the rule by about a second and reload the issue date before proceeding.  Please try that and let us know what happens.

[Rasneet Kanwar]

 @Bill Sheboy  Thanks! Adding Re-fetch Issue Action worked for us! We've learnt something good today. 

Regards, Rasneet

[Trudy Claspill]

@Bill Sheboy should get credit for this answer. :-)

[Rasneet Kanwar]

Hi @Trudy Claspill and @Bill Sheboy 

Thank you for being patient with me and helping us out. Your suggestions taught us a lot and it feels great to be a part of this community.

All your efforts are very much appreciated!!

Best Regards, 

Rasneet