nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Smartvalue for Trigger in Automation

Flavien Gache

Hello everybody.
For a quite complex case of automation, I would like to know if it is possible to access linked issues for the parent issue of the issue that triggered an automation.

The aim is to take this value and copy it in a work item created in that same rule.
I think it is not possible (i failed at finding it) but I would like a confirmation.
Thanks in advance !

Accepted answers

Bill Sheboy

Hi @Flavien Gache

Yes, that is possible, in several ways...

When you need just the keys for the work items, one could use the Lookup Work Items action twice: once to get the parent's data (i.e., the issuelinks), and then use another lookup with dynamically generated JQL for the action from that smart value.
When you need to access / modify the work items, as with above, use one Lookup Work Items action to get the parent's smart value, and then branch on dynamic JQL to them directly.
Or a variation of above to access the work items, branch directly to them with JQL and using the linkedIssues function: issue IN linkedIssues("{{triggerIssue.parent.key}}") perhaps adding other criteria for link types, etc.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Flavien Gache

Yes, that is possible, in several ways...

When you need just the keys for the work items, one could use the Lookup Work Items action twice: once to get the parent's data (i.e., the issuelinks), and then use another lookup with dynamically generated JQL for the action from that smart value.
When you need to access / modify the work items, as with above, use one Lookup Work Items action to get the parent's smart value, and then branch on dynamic JQL to them directly.
Or a variation of above to access the work items, branch directly to them with JQL and using the linkedIssues function: issue IN linkedIssues("{{triggerIssue.parent.key}}") perhaps adding other criteria for link types, etc.

Kind regards,
Bill

Jean Horn

👋 Hello,

I don't quite understand what you need. ~ 🤔

Would you like to get the issues linked to the parent issue, which is calling the automation?

Thank you.

Flavien Gache

Thanks for the answer (and sorry for my late reply). I tested your lookup solution and it seems to work so thanks !
In the meantime my client change ideas and won't use it... but i certainly will in the future for other use cases.
Have a good day

Flavien Gache

Yes that would be it. I succeeded in my automation thanks to Bill answer
Thank you too for taking some time to write followup questions, I appreciate Have a wonderful day, friend.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud