Script to have more than one option for initial status

Shawn Smith March 11, 2014

I'm looking for a way to have more than one option for initial status, so that when users log an issue they can set the initial status to either "Open" or "Ready" - i.e. a regular status and a fast-track status.

Currently this takes two steps. The initial status in our workflow is "Open" and users often forget to change the status of important and well-defined issues from "Open" to "Ready."

I'm looking for a way to enable this from the Create Issue screen, perhaps by adding a custom field to the Create Issue screen, and then creating a script or post-function that sets the initial status to either Open or Ready based on the value entered for that field.

Importantly, our JIRA is not self-hosted, so we need a solution that works for OnDemand.

2 answers

1 accepted

3 votes
Answer accepted
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 12, 2014

You mention in your tags script runner and JJupin, but neither plugin is available in OD.

You can do this without using a plugin by setting a condition on your Ready transition that checks the required fields are filled, and then use the "auto" property on the transition - more info here: https://answers.atlassian.com/questions/49747/what-is-your-most-valuable-jira-trick

Jelly escalation is also not available in AOD...

Filipe March 12, 2014

You are right, i didn't saw we were talking in OD.

Your solution look great.

Thx

Radu Dumitriu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 12, 2014

Thanks Jamie

The thing with onDemand is that, from what we measured, the technology really will lack performance when it comes to scripting. The amount of communication is just too big, and not all stuff will be available.

I tried to propose sanboxed instances on onDemand, but the thought was rejected w/o further comment (understandably).

0 votes
Filipe March 11, 2014

Hi Shawn

"Currently this takes two steps. The initial status in our workflow is "Open" and users often forget to change the status of important and well-defined issues from "Open" to "Ready."

If they are well defined why don't you use

https://confluence.atlassian.com/display/JIRA/Jelly+Tags

https://confluence.atlassian.com/display/JIRA/Jelly+Escalation

Setting a service to run a jelly script i na given period of time ( secounds) that would catch "those well-defined issues" that are open and automatly make the transition of the issues to the state you need.

Regards,

Suggest an answer

Log in or Sign up to answer