Hello all,
I need help with one task related to JIRA Automation.
Scenario:
I have 10 or more main/parent tasks. Each of them contains exactly the same number of sub-tasks, with exactly the same naming convention. I'm preparing a rule that after changing the status of one of the sub-task will change the status of another sub-task. Since each subsequent created main/parent task will have exactly the same sub-tasks, with the same names, I generally use assumptions related to the names. The rule works, but unfortunately, it changes the status of subtasks from each main/parent task.
Now, according to my rule, when I change status of Sub-task A from Task 1 it changes status of Sub-Task B from Task 1 (according to expectation), but in the same time it changes status of Sub-task B from Task 2 and Task 3.
The question is, what I have to add to my rule so that the rule only works on sub-tasks from one main/parent task. So, when I change status for Sub-Task A from Task 1 it only changes status for Sub-Task B from Task 1.
I will be grateful for your help :-)
Thanks
Hi Przemek,
I think you want to edit sub-task of specific trigger task issue.
Please try "New branch" which could action on other related issue.
And choose "JQL" condition to filter your target issue.
I think maybe the problem is that JQL didn't response the correct issue object.
regards,
Iris Chen
Try this JQL "linkedissue" to limit the scope and filter your target issue!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Iris,
That can works, but unfortunately/probably this will require separate rule for each main task. And every time I will create a new main task, I will have to create/adapt rule for this new main task.
And this is what I want to avoid.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Przemek,
I am not sure if it work, but try to use action "Lookup issues" first to get the main issue key.
Then use branch to filter your target sub-task issue.
See the example below. Hope it helpful.
regards,
Iris Chen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Iris,
Thank you for constantly support :-)
It's seams that I have different version of JIRA or something because I don't see this action on my list :-(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.