Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-15276

Simplified Workflow: add option to disable the creation of new statuses

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • 29
    • 11
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      As a JIRA administrator,

      I'd like to be able to disable the creation of new statuses by standard users through the Simplified Workflow's 'Add Status' button

      so that I can:

      • avoid the creation of effectively duplicated status names like "To Do" & "TODO", or Testing & Test & Tested & In Test & Integration Test
      • make easier multi-project JQL queries to retrieve meaningful info based on statuses
      • make more maintainable the order in which statuses are displayed in gadgets and JQL ORDER BY clause.
      • avoid the creation of statuses for trying to store info when it would be better to use anything else instead (labels, the resolution field, a custom field...)

            [JSWCLOUD-15276] Simplified Workflow: add option to disable the creation of new statuses

            Related to JSW-15452

            Ignacio Pulgar added a comment - Related to  JSW-15452

            Hi Dave,

            Thank you for having moved this issue to a more suitable project.

            The Simplified Workflow is absolutely great and will alleviate JIRA admins workload considerably.

            However, lacking an option to avoid the creation of new statuses by users distinct from JIRA Admins prevents us from starting using it.

            Unlike labels, statuses suggested for autocompletion are not scoped within those used on projects that users have permission to view.

            This will mean that, after some time using the Simplified Workflow on all Software projects, the instance will have hundreds of statuses, some of them with similar names with slightly different spelling, confusing users on which status they should use.

            Cheers,

            Ignacio Pulgar

            Ignacio Pulgar added a comment - Hi Dave, Thank you for having moved this issue to a more suitable project. The Simplified Workflow is absolutely great and will alleviate JIRA admins workload considerably. However, lacking an option to avoid the creation of new statuses by users distinct from JIRA Admins prevents us from starting using it. Unlike labels, statuses suggested for autocompletion are not scoped within those used on projects that users have permission to view. This will mean that, after some time using the Simplified Workflow on all Software projects, the instance will have hundreds of statuses, some of them with similar names with slightly different spelling, confusing users on which status they should use. Cheers, Ignacio Pulgar

            Hi ignacio.pulgar,

            As simplified workflow is specifically a feature of JIRA Software, I've moved it to this project.

            Cheers,
            Dave Meyer

            Dave Meyer added a comment - Hi ignacio.pulgar , As simplified workflow is specifically a feature of JIRA Software, I've moved it to this project. Cheers, Dave Meyer

            Ignacio Pulgar added a comment - Related to https://jira.atlassian.com/browse/JSW-8845

              Unassigned Unassigned
              5c52af3a81d4 Ignacio Pulgar
              Votes:
              55 Vote for this issue
              Watchers:
              38 Start watching this issue

                Created:
                Updated: