Can't find Portfolio fields in Automation for JIRA

[Eshita Seelam]

Hello,

We are on JIRA Data Center (version 8.20.10) and are pilot testing Automation for JIRA plugin (8.1.1) in Dev JIRA.

We do not find any advanced roadmap fields such as parent link/ Initiative Link/ Capability link in the dropdowns for conditions or actions. (issue fields condition or create issue action or edit issue action).

We are trying to achieve an ask where in we can get a list of all the child issues of all the Capabilities in project XYZ. If there are 8 Capabilities in project XYZ, the query should return all the Epics, Stories, sub tasks underneath all the 8.

Could you help suggest if we are missing anything.

[Bill Sheboy]

Hi @Eshita Seelam 

I do not believe all of those fields are available yet for automation rules, as described in this suggestion: https://jira.atlassian.com/browse/JIRAAUTOSERVER-135

To see which smart values are available in your instance/issues, please try this how-to article: https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html

Kind regards,
Bill

[Eshita Seelam]

Hi Bill,

Thank you for sharing the links. 

Will upvote the suggestion and go through the article.

[Ste Wright]

Hi @Eshita Seelam 

Those fields aren't readily available, but that does not stop them being referenced using Smart Values!

We'd be happy to help create the rule with you if needed! What is the outcome you'd like the rule to achieve? Based on your initial question, it seems like...

• Part of your hierarchy is Capability > Epic > Story > Sub-task
• These should be sent as a list

...but who should they be sent to? Should it be via email? And what should trigger the list to be sent?

Ste

[Eshita Seelam]

Hi Stephen,

Thank you for answering that.

Our hierarchy includes Initiative > Capability > Epic> Story > Sub-task.

We will need to send a mail of all the underlying issues (Capabilities to Sub tasks) of the Initiatives in a project to a particular user (let's say one of the admins in the project) in the form of a list. The trigger could be a scheduled one governed by a CRON expression.

If possible, could this list contain other fields as issue key, summary, assignee, reporter, issue type.

Priorly, we used a Power script and triggered it via a JQL. The respective user would subscribe to that JCL at their desired interval. So, we are looking for something similar using Automation for JIRA.

[Ste Wright]

Hi @Eshita Seelam 

Thanks for this information - a few more queries...

• How would these lists be formed? Is it just a list of all the issues regardless of order? Or is this an ordered list of issues under their respective parents?
• Do you have any Apps with additional JQL functions? For example, Scriptrunner?

Ste

[Eshita Seelam]

Hello Stephen,

Apologies for the delay, we were busy with our standardization process.

• They are all unordered issues under the parent of the specified project. The project used to be provided as an argument while running the script, and it would fetch us a list of all the issues under all the initiatives in that project.
• We do not have Script Runner, but we do have Power Scripts for JIRA.

Thank you!