Stop Create Issue from allowing Status to be selected

[Doreen Miller]

When creating an issue, we now have the option to set the status.  This causes a problem for my workflow.  We allow transitions between any states, however, I need all issues to be created with the NEW status.  Is there an easy way to disable the ability to set the status on issue creation for a single project?

[Jack Brickey · Accepted solution]

HI @Doreen Miller , yes this is a new feature being rolled out now that I wish was defaulted to off personally.

Here is an article that will answer your questions - Set-the-status-of-an-issue-while-creating-it 

In a nutshell...

• Go to Settings > System.

• Select Edit Settings.

• Scroll to Options and disable Status
  

• Select Update to save your changes. Settings

[Doreen Miller]

Can this only be controlled at the system level?  Are we able to control it at the project level?

[Jack Brickey]

It is currently at the system level. I haven't seen any plans to change that though I noted a number of comments on that Post that I provided regarding this.

[Doreen Miller]

Jack, thank you!

[Trudy Claspill]

Actually, in the change request that enabled this feature:

https://jira.atlassian.com/browse/JRACLOUD-69559

...the comment on Jan. 22 from Amira Badran indicates they are continuing to work on a way to make this configurable per project.

Amira Badran added a comment - Yesterday

Hi everyone, 

We are glad to inform you that the Status in Create issue has been shipped to all customers not on release tracks. We have enabled it by default as we saw a lot of potential in the value it would bring to our users, and we didn't want anyone to miss out and never know it existed. We did, however, want to make it very easy to switch off because we know changes like this can sometimes cause problems.
To remove the feature from the Create issue across all projects in your instance:

1. Go to Settings > System.
2. Select Edit Settings.
3. Scroll to Options and set the Status setting to off.
4. Select Update to save your changes.

We will continue to work on making this feature more configurable and specific to individual projects. Thank you for your feedback, and we look forward to hearing your thoughts on the feature.

Thanks,
Amira Badran
Product Manager, Jira Software Team

[Jack Brickey]

Nice...thanks for sharing!

[Nic Brough -Adaptavist-]

If you don't want to turn it off for everyone, then you can do it in the workflow.  It's a bit of a slog, but you'd need to replace every "all" transition with a new (shared) transition that comes from every other status in the flow.

[Doreen Miller]

Yeah, I was assuming this new feature would respect the restrictions of the workflow.  I was hoping to avoid doing that since I have two projects and one of them has more statuses that I'd like.  I inherited the projects and neither of them is configured very cleanly.  I've slowly been cleaning them up.  But cleaning up the statuses one of the projects use is a bit of a big task.

We had a sync meeting with all the product owners and scrum masters in the company today.  Luckily everyone agreed we could turn it off at least for now.  Whew.

[Nic Brough -Adaptavist-]

Technically, it is respecting the workflow - a user has create permission and an "all" transition into the status.  It's a terrible implementation.

When it was announced, I had to turn it off in dozens of systems, and then explain how to find and clean up the mess it had made.

If it had been implemented properly, it would have been fine.  A setting in the workflow editor that has tick-boxes next to each status to say "and let people create issues in this status", or the ability to add many transitions from create to another status.

[Doreen Miller]

I agree.  Any kind of setting that provided more control over it would have been nice.  At my previous company, there would have been teams that would have liked this feature and others that couldn't have lived with it.  It really depends on what your process is.

[Nic Brough -Adaptavist-]

I think it is a great idea, I can see lots of uses for it.

But only if defaults to "off".  It should have been opt-in, not opt-out.  And the admin UI is wrong too, as it does not make it clear.