Get fields from Epic Parent Link (Initiative)

[Melissa C]

Hello Jira People!

Data Center v 9.12

In my group we use Initiatives and will link Epics from different Projects to Initiatives using the Parent Link.  This allows us to see all Epics in an Initiatives. 

I have an automated email that will send updates when the Status of Epic changes. In that email I would like to include fields that in in the Initiatives. For example, in the Initiative we have a field for Customer Communication needed Y/N.  

In my report I want to include the Epic-123, which is linked to Initiatives-456, Has Customer Communication Needed = Y

I'm able to get the Initiative Key but using {{customefield_12346}}, but how do I get the Customer Communication Needed value.  I tried {{customefield_12346, customefield_654321}}, I've also tried {{customefield_12346, CustomerCommunication}}

Any other suggestions?

[Melissa C · Accepted solution]

After lots of research and reading! I stumbled on the answer.  An Automation is defaulted to be single project.  You will need to change the setting for the individual Automation to allow Multiple projects or Global. 

Go to Rule Details-> Scope -> Change From "Single" to "All Projects" or choose which projects you need to include -> Save  

"When you want your rule to access issues in another project, change the scope in the details at the top of the rule to multiple-project or global.  Your Jira Site Admin will need to help with that in the global settings as such rules can have a larger impact on your site."

Thank you for going above and beyond.

Hopefully, this answer helps someone out there. 

@Trudy Claspill  - Thank you for all your suggestions

[Trudy Claspill]

Hello @Melissa C 

I don't have a Data Center environment where I can try this, but try...

{{customfield_123456.name of your customer communication field}}

[Melissa C]

Thanks @Trudy Claspill 

I tried that :-(

"I'm able to get the Initiative Key but using {{customefield_12346}}, but how do I get the Customer Communication Needed value.  I tried {{customefield_12346, customefield_654321}}, I've also tried {{customefield_12346, CustomerCommunication}}"

[Trudy Claspill]

Hello @Melissa C 

Neither of your examples match what I suggested.

Your examples use a comma and a space.

{{customefield_12346, customefield_654321}}

My suggestion uses a period and no space after it before the secondary field name.

{{customfield_123456.name of your customer communication field}}

Also, I just noticed you have an extraneous "e" in your examples:

{{customefield_12346, customefield_654321}}

And if you choose to use the field name rather than the field id, you must use the exact case and blank spaces as are used in the field name. If the field name is "Customer Communication Needed", then you would need to use:

{{customfield_12346.Customer Communication Needed}}

[Melissa C]

@Trudy Claspill 

Thanks for your suggestions. Here are some of the smart values that I tried.  It appears that the only smart value I can get is the key, I've tried other fields, and they do not give any results.  I wonder if the issue is that we are using the Initiative Issue Type and we add Epics as Children of the Initiatives.  We do this using the Parent Link in the Epic. This way when you look at the Initiative you will see all of the Epics associated to Initiative.

@Bill Sheboy - any Suggestions 

This gave me the Parent Key {{customfield_23880}}

{{customfield_24484}} - Customer Communication 

---

I have tried these variation of the field  

{{customfield_23880.customfield_24484}}

{{customfield_23880.Customer Communication}}

{{issue.parent link.customfield_24484}} 

{{customfield_16680}} - Tried a different field besides the Parent Key and Customer Communication 

{{customfield_23880.customfield_16680}} - This was testing a different field besides Customer Communication 

{{issue.parent link.customfield_23880}}

{{issue.parent link.customfield_23880.id}}

{{issue.Parent.Link.data.key}}

{{issue.parent link}}

{{triggerIssue.parent}}

{{issue.parent.issuetype}}

{{issue.Epic.self}}

{{issue.parent}}

{{issue.customfield_23880}}

{{issue.parent.priority.name}}

{{issue.parent.Epic Link}}

{{issue.parent.epic.summary}}

{{issue.customfield_23880.name}}

[Trudy Claspill]

Hello @Melissa C 

I found a data center instance where I can do some testing.

What version of Jira Data Center are you using?

Can you provide screen images that show your complete automation rule? It may inspire some ideas about a way to solve your need.

[Melissa C]

@Trudy Claspill 

Thank you!! We are using 9.12

Will provide screenshot