Forums

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

Custom field filled automatically with Automation for Jira in Portfolio Hierarchy

Marco Brundel
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 13, 2018

We use Automation for Jira, Portfolio for Jira en Jira Software. In Jira we use the following Portfolio hierarchy:

 

  1. Theme
  2. Initiative
  3. Epic
  4. Story
  5. Sub-task

 

On a Theme we have a custom field (customFieldId=10200, name = Program).

 

Now, from the Theme, I want to have the Program field filled automatically in the underlying issues in this hierarchy.

 

What is the best way to do this?


When Scriprunner offers a better possibility, I also like to hear it

2 answers

1 accepted

0 votes
Answer accepted
John McKiernan
Atlassian Partner
November 13, 2018

Hi Marco, 

thanks for your question (and the clarity with which you have asked it!) 

With Automation for Jira, this is not something we can do at the moment. We have an existing improvement issue to support multiple levels of hierarchy. I have added a vote to it on your behalf. 

https://codebarrel.atlassian.net/browse/AUT-309

Cheers,

John 

Edwin Stol
Contributor
November 20, 2018

Hi @John McKiernan1,

We managed to resolve it as follows, with a combo of ScriptRunner and A4J:Project_automation_-_Jira.png

Like # people like this
John McKiernan
Atlassian Partner
November 20, 2018

Hey Edwin,

this makes a lot of sense. Glad you found a workaround and thanks also for sharing it on the community :)

Cheers,

John 

Like # people like this
0 votes
Mike Headley
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 1, 2023

In case anyone's looking to do this on a company-managed Jira Cloud instance: I used the same general structure of the previous answer and added on / updated a few of the queries. Interestingly, smart values seem to have come a long way and I was able to do things well outside of the documentation. For example, I was able to grab the Theme name from the Epic level using the smart value {{triggerIssue.parent.parent.summary}}

For context, I wanted to map 3 custom fields whenever any of the issues in the hierarchy update their parent link:

Portfolio = Theme

Program = Initiative

Project = Epic

 

Screenshot 2023-02-01 at 3.20.30 PM.pngScreenshot 2023-02-01 at 3.21.35 PM.pngScreenshot 2023-02-01 at 3.22.14 PM.png

Suggest an answer

Log in or Sign up to answer