Hi @Massimiliano Stretti and welcome to the Community!
That is a very strange requirement. The list of linked tasks is visible on your issue just below the description, under linked issues. Could you explain why you would want to repeat that information in your description field (of all places 😛)?
Sorry for challenging your requirement rather than just giving your an answer ...
Hi, After linking the tasks, the state change triggers 4me, passing the description as a parameter. We need to have a description constructed automatically to have a defined structure ([id] description)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I still don't quite get what you're trying to do, @Massimiliano Stretti.
You can use the Lookup issues action in your automation, using JQL to get a list of linked issues.
After doing that, you can use the {{lookupIssues}} smart value to add information to your description. Still, if you are going to that on every transition your issue goes through, I don't see how this would be beneficial or clear in any way.
Anyway, to edit your description, you would add an edit issue action, with the following smart value:
{{#lookupIssues}}
* {{key}} {{summary}}
{{/}}
For more details, check out Jira smart values documentation and locate the lookupIssues smart value.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have a release automation project. It involves having a story on Jira with linked tasks that enter a release. When the task is moved to the 'to approve' status, an automation contacts 4me and opens an approval workflow. 4me returns an ID, which we write into the story, and we wait until the workflow is approved. When we call 4me to create the workflow, we pass the notes, or description, so that the approvers know what they are approving. We already have all of this set up. What we would like now is to have the notes automatically filled in rather than manually.
Now I have developed an automation, separate but to be integrated into the existing one, which adds the description of the linked task to the story.
I'm having trouble understanding which components to use for iterating through the tasks linked to the story and how to add the fields of the linked tasks to the description of the story.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, I tried what you suggested. I used Lookup Issues for my task RM-47.
But lookupIssues selects the same task, I need to find the tasks linked to my RM-47. In RM-47 task i need info of "childs" RM-56 and RM-76.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, found the solution.
JSQ is: issueLink = {{issue.key}}
All the rest is Walter solution.
Thank you very much Walter!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.