Automate field setting for each issue of lookupIssues with version created as trigger

[Sebastian Klie]

Hello all together!

I'm currently on the search to find a simple solution to reset a list of issues as soon as a new version is created in Jira.

We are a small start-up and are in the need to run a testplan on every new release version as long as we do not have a proper QA. So for our testphase I want the possibility to just reset a bunch of test tasks whenever we create a new version.

I tried to gather all issues in the Jira automation flow with lookupIssues.

Now I am stuck because I do not have a parent issue as the "version created" trigger can occur outside of an issue.

My Question is: How can I iterate over the list of {{lookupIssues}} and do the action "transition to" for each issue in the list?

My current unfinished solution looks like this:

Yet I'm unable to access the smart value {{issue}} nor can I somehow add custom actions.

[Hana Kučerová · Accepted solution]

Hi @Sebastian Klie ,

welcome to the Atlassian Community!

I would recommend you to replace two components (Lookup issues and Advanced branching) with one component (Branch rule / related issues -> Type of related issues: JQL - here you can add "project = MG AND type = Task").

The second thing I would recommend you to not change already processed issues, but create new set of issues for testing the new version (if possible).

[Sebastian Klie]

Hey @Hana Kučerová 

thank you for your help.

I was able to solve it based on your answer.

My current solution is to have an epic for each test step. Whenever a new version is added a new task for each epic is created and added to a new sprint with the new release version as fixVersions.

It is not optimal but works for now.