Editable status on item create screen - ignore workflow

[Goran Dermeta]

Has anyone noticed a change from 2 weeks ago, where anyone can change status at item creation?

Fix "Create" Button Visibility in Jira Company Managed Boards 

Today i lost 1 hour of checking screens, automations and then talk with Rovo, so that he told me after 5-6 prompts that this is something new, response here:

You’ve run into a (relatively new) global Jira setting, not a project/workflow misconfiguration.In Jira Cloud there is now an option that, when enabled, lets users choose any reachable status at issue creation on boards for company‑managed projects. That’s exactly what you’re seeing: even though CI Task Workflow’s initial status is BACKLOG, the global setting is allowing Status selection on create, and it affects all projects.You can turn this off at the global level so Status is no longer editable on create anywhere.

Yeah, that setting is… controversial.

You’re absolutely right:

• It was easy to miss (buried in General configuration).

• It changes a very core behavior of Jira.

• The default being effectively “enabled” for many sites means admins suddenly see users picking any status on create, which breaks carefully‑designed workflows like your BACKLOG‑first setup in CICOOK.

Why Atlassian added it (theoretical use cases)

From Atlassian’s side, the main use case is probably:

• On a board, let a user click “+” in any column and create the issue directly in that column’s status.
  For example: create a quick “Done” ticket for something they already finished, or create a “Blocked” item straight into that state.

On paper, that helps some very lightweight teams who treat Jira as a simple board and don’t care about strict process. But for any team that:

• Uses backlog grooming,

• Has SLAs / reporting based on time in status, or

• Treats workflow as a controlled process,

it’s pretty harmful: people can bypass the initial status and all upstream transitions.

What you did is the “best practice”

For a structured setup like yours, you’ve picked the right approach:

• Turn the option OFF globally.

• Enforce where issues start via workflow initial status (BACKLOG).

• Let issues move only via transitions (and automation where you define it).

That keeps your data predictable and your reports meaningful.

If you want to give this feedback upstream, you can:

• Use “Give feedback” in the Jira UI (bottom‑left help menu), or

• Comment / vote on public suggestions in Atlassian’s public Jira (https://jira.atlassian.com) about:

  • Default being OFF

  • Needing a per‑project toggle rather than global.

If you ever see another Jira behavior suddenly look “magical” or global like this, feel free to throw it at me—I’ll help you track down where in the admin maze it lives.

[Staffan Redelius]

Hi @Goran Dermeta 

Thank you for your thorough description of this. It sounds.... well not like a good solution.

What happends to all the validations and conditions downstream in the workflow? Can you bypass them when creating the issue?

I really don't like these things to be turned on automatically for all projects without having a say as an administrator. 

PLEASE Atlassian don't do it this way!

EDIT:

When looking up the link it says this is only for workflows where you allow global transitions (from any status to any status) and that answers my question.

With that said if if your workflow doesn't support a defined process you might as well be able to create a ticket to any status.

I still don't like features to be turned on automatically, please give me the option to opt-in if it is relevant for the organizaton.

Best regards,
/Staffan