Automation Rule to transition issue without knowing current status of issue.

Question

I developed an automation rule aimed at transitioning an issue to a REVIEW status; however, the rule's effectiveness is hindered by my lack of knowledge regarding the issue's current status. This limitation means the rule only functions correctly when the issue's present status is directly linked to the REVIEW status. To circumvent this, I'm contemplating the feasibility of retrieving the issue's current status. This would potentially enable me to systematically transition the issue through intermediate statuses until it reaches REVIEW. However, I'm uncertain about the practicality of this approach within the context of Jira Data Center, even though I have ScriptRunner at my disposal. Is there a viable method to implement this process effectively?

carlos andrade_kuc0lo · Answer

Brilliant! Thanks so much Kalyan!

Kalyan Sattaluri_iinm1n · Answer

hey @carlos andrade

If you look at the second rule steps above, especially the condition section, the last action is that once we transition an issue to "In Dev", we call the same rule again, this time it will transition it from "In Dev" to "Review".

* Condition - If {{lookupIssues.status}} equals to "Analysis"
* Action - Transition to "In Dev"
* Action - Send webrequest to this same rule with issue key to transition to next step.

If you have not worked with webrequest / webhook before, I suggest you first:

* Get an access token first (see here),
* Then you start with rule 2, with trigger = incoming webhook. At this point you just need the URL from this rule so after you have the trigger, and set up an action -> log action and capture {{webhookData}}. Thats it, give it a name and publish.
* then start working on setting up rule #1

* In rule #1, first step is easy, set up scheduled trigger. give one issue in JQL such as key = KKJK-123, of course this issue should not be in "Review" status
* In action of rule #1, then you will choose action -> send webrequest, use the URL from rule #2 above, then give your credentials and do a POST to that endpoint with payload like below:
* { "key" = "{{issue.key}}" }
* Then run the rule #1 and checks logs of both rules, if rule 1 is successful, you will see in rule #2 the payload you sent...

above is the prerequisite. if you can do until here... then your rule #2 you can complete.

I can guide you on next steps but try above and share screenshots so I can help you if you get stuck.

carlos andrade_kuc0lo · Answer

>>To clarify, you know your possible transition options correct?

Yes. I know all the possible transitions options.

Thank you so much! I was thinking along those lines.

Will this work if the issue is currently in "Analysis"? Will it transition it first to "In Development" and then to "Review"? Would it transition twice in the same rule execution like you have it in your example?

"Analysis" -> "In Development" ->"Review"