Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-15276

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

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 24
    • 5
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features 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...)

          Form Name

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

            Hi teams!
            This is a workaround that reportedly worked for some customers.

            You may want to validate at your UAT instances‚ maybe it's helpful to you too. You may add this to the announcement banner:

            <!-- COMPANY-NAME custom announcement banner CSS to prevent Status creation from Agile Boards (Workaround to JSWSERVER-15276) -->
            <style>
            #ghx-dialog-create-status form, #ghx-dialog-create-status button {
              display: none;
            }
            
            #ghx-dialog-create-status h1::after {
              content: '(disabled by Jira Admins)';
            }
            
            #ghx-dialog-add-column form, #ghx-dialog-add-column button {
              display: none;
            }
            
            #ghx-dialog-add-column h1::after {
              content: '(disabled by Jira Admins)';
            }
            </style>
            <!-- End of workaround to JSWSERVER-15276 -->
            

            Please change COMPANY-NAME by your company and keep the comments, as a best-practice.

            Also please review How to customize Jira with JavaScript and CSS to understand the caveats and disclaimers on such customizations that are unsupported and provided always as-is to be applied at the Jira Admins' own discretion.
             
            Cheers

            Rodrigo Martinez added a comment - Hi teams! This is a workaround that reportedly worked for some customers. You may want to validate at your UAT instances‚ maybe it's helpful to you too. You may add this to the announcement banner: <!-- COMPANY-NAME custom announcement banner CSS to prevent Status creation from Agile Boards (Workaround to JSWSERVER-15276) --> <style> #ghx-dialog-create-status form, #ghx-dialog-create-status button { display: none; } #ghx-dialog-create-status h1::after { content: '(disabled by Jira Admins)' ; } #ghx-dialog-add-column form, #ghx-dialog-add-column button { display: none; } #ghx-dialog-add-column h1::after { content: '(disabled by Jira Admins)' ; } </style> <!-- End of workaround to JSWSERVER-15276 --> Please change COMPANY-NAME by your company and keep the comments , as a best-practice. Also please review How to customize Jira with JavaScript and CSS to understand the caveats and disclaimers on such customizations that are unsupported and provided always as-is to be applied at the Jira Admins' own discretion.   Cheers

            This causes us constant headaches. The ability to turn off or at least limit this functionality would save us an incredible amount of time (not to mention headaches!)

            Robin Powell added a comment - This causes us constant headaches. The ability to turn off or at least limit this functionality would save us an incredible amount of time (not to mention headaches!)

            PLEASE. I want to allow the simplified workflow, but only allow users to select from the existing statuses. 

             

            Aaron Matthys added a comment - PLEASE. I want to allow the simplified workflow, but only allow users to select from the existing statuses.   

            This is also causing an issue for our company, we need the option to be able to stop board admins from creating a status on simplified workflows as the workaround to move all workflows over will be a large project

            Collette Gray added a comment - This is also causing an issue for our company, we need the option to be able to stop board admins from creating a status on simplified workflows as the workaround to move all workflows over will be a large project

            We have been asking for this for nearly 2 yrs now. We have an EA with Atlassian and yet we have no traction on this. It's causing a lot of issues.   Why can't we get traction on this?  

            Jennifer Hall added a comment - We have been asking for this for nearly 2 yrs now. We have an EA with Atlassian and yet we have no traction on this. It's causing a lot of issues.   Why can't we get traction on this?  

            Peter Andréasson added a comment - - edited

            The workaround that we use in our setup is to always have a dummy project created next to the original one by shared project config and by that the simplified option to add statuses is blocked. We can follow this principle as we try to just use shared Jira configurations as far as possible. 

            Peter Andréasson added a comment - - edited The workaround that we use in our setup is to always have a dummy project created next to the original one by shared project config and by that the simplified option to add statuses is blocked. We can follow this principle as we try to just use shared Jira configurations as far as possible. 

            Erki Tammik added a comment - - edited

            This feature is causing problems now that users can easily create statuses for their projects. I find myself copying workflows to remove unused and duplicated statuses.

            It is unacceptable that Jira administrators do not have control over it, as it creates more work for us to manage. We need a solution for this.

            Erki Tammik added a comment - - edited This feature is causing problems now that users can easily create statuses for their projects. I find myself copying workflows to remove unused and duplicated statuses. It is unacceptable that Jira administrators do not have control over it, as it creates more work for us to manage. We need a solution for this.

            Any updates? 

            Jennifer Hall added a comment - Any updates? 

            Any updates?

             

            Niklas Kordasch added a comment - Any updates?  

            I wasn't able to find a version of this for Cloud, so I created and linked https://jira.atlassian.com/browse/JRACLOUD-73833.

            Esther Strom [ACP-JA] added a comment - I wasn't able to find a version of this for Cloud, so I created and linked  https://jira.atlassian.com/browse/JRACLOUD-73833 .

              Unassigned Unassigned
              5c52af3a81d4 Ignacio Pulgar
              Votes:
              198 Vote for this issue
              Watchers:
              100 Start watching this issue

                Created:
                Updated: