I want to transition an issue automatically between 2 statuses, each time it is commented on by the assignee, so that it assigns to alternating parties while waiting for their response.
I have a simple workflow that consists of "Waiting for Vendor" and "Waiting for Developer", and "Closed" statuses.
I'm using 2 automation rules in the JIRA Automation plugin to listen for IssueCommented and transition the issue appropriately
This works as expected, except for one thing.
... perfect... but when I refresh the page...
According to history - the automation is
WHY does #3 happen. I feel that by all logic it should NOT, because:
Hi
Maybe it's missing in your description, but in :
2. "Developer Comment" rule
- Everything same as Vendor Comment rule except:
- JQL is: issuetype = "A Subtask" and status = "Waiting for Developer"
- Transition (from "Waiting for Developer" to "Waiting for Vendor")
do you have the "Disable Notification = Yes" ? If not, that might be the reason why it immediately jumps back and forth.
What is also interesting in your setup is the fact that both of your rules react on "Issue commented" event. At the time of execution, the rules are evaluated somewhat sequentially (in order they were updated or created). So if your rule 1 changes the status and then rule 2 is evaluated in the same loop, it is immediately applied.
I have tried this with Disable Notification = Yes and that makes no difference. I appreciate the insight about the processing... I may support a Jira.atlassian.com support issue to fix this... because by all indications in documentation this problem should be prevented by my JQL that specifically indicates the status on which the automation should be applied.
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.