can we have multiple initial status in workflow ?

[Ramesh Udari1]

Hi,

We have encounter with a situation that we want to switch between different status based on custom field value at issue creation page, is it possible in JIRA ?. If not, is there any customized way to achieve it, your suggestions are highly appreciated. 

Our use case:

We have a Project A and associated with workflow, which has "Open" as a initial status, but we want to change initial status from "Open" to "Pending", if user selects custom field value as "Yes" in issue create screen.

[Tomasz Stec]

Hi,

Indeed, there is no way to have multiple initial workflow statuses in JIRA, but there is a workaround which i successfully implemented in JIRA:

1. You need to have create screen with custom field (i recomend custom field type: select)
2. Prepare workflow similar to this:
   multiple-initial-statuses.PNG
3. Then add custom postfunction (i used here Script Runner postfunction)
   create-post-function.PNG
4. Implement post function to get custom field from 1. and for its different value perform different transition (init1,init2 or init3).

It's kinda 'magic' but belive me it works 

[Ramesh Udari1]

HI Tomasz, I tried it is not working.

[Nic Brough -Adaptavist-]

It is a simple "no".  A transition always has a single target.

The closest you can get to this is to land on the created status, and trigger an immediate second transition to the other status.  There are a couple of addons that let you do this.

[Ramesh Udari1]

Hi Nic, Thanks for you response on it. Could you please provide some links of these add-ons. And also we would like to handle this with listener with "create" event. Is it possible or not?. are there any event or issue life cycle method which trigger immediately after issue has been created. So that we put our trigger code in that extension point.

[Nic Brough -Adaptavist-]

I've always used the script runner addon to do it.

[Ramesh Udari1]

Hi Nic, Can you please provide me sample of script runner

[Sateesh Chandra]

The only option you see is "Instead of letting user update the user custom field, you can configure a issue transition for Yes and No and then start continue with other issue transitions"

Initial status -> open

open -> Yes -> <destination status "Pending">

open -> No -> <any other status you prefer>

Am I clear?

[Ramesh Udari1]

Hi Sateesh, It;s clear, but we do not want any manual intervention. We want to do immediately once issue is created autometically.