Uploaded image for project: 'Jira Work Management Cloud'
  1. Jira Work Management Cloud
  2. JWMCLOUD-303

Allow users to add/remove columns directly in Company-Managed Business Boards

XMLWordPrintable

    • 12

    • 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.

      Issue Summary

      Allow users or administrators to add/remove columns from Company-Managed Business Boards like in Team-Managed Business Boards directly in the Board or Board Settings

      Steps to Reproduce

      1. Access a Company-Managed Business Board
      2. Try to add/remove a column

      Expected Results

      Jira allows the user or administrator to add/remove columns directly at the Board

      Actual Results

      There is no way to add/remove columns directly at the Board

      Workaround

      Follow the How to create workflows for company-managed projects documentation 

            [JWMCLOUD-303] Allow users to add/remove columns directly in Company-Managed Business Boards

            Rodolfo Romero - Adaptavist added a comment -

            These are some of the reasons why we need this feature to be added to company-managed business projects:

            • Team-manage projects supports this feature.
            • Company-manage software projects support this feature in Server and Cloud.
            • If a project contains different workflows for different issues types, which is a very normal case in a company-managed project, only one workflow can be mapped to the board. How do we track the other workflows in the board? In the current situation, this is not possible.
            • Migrations from Server/DC to Cloud are broken because business projects cannot be migrated to a Cloud company-managed business project that lacks of a feature that has always been there.
            • In the current scenario, if a column needs to be renamed, the whole workflow needs to be modified as changing the name of a status in the existing workflow will impact globally other workflows in the system. This means that the only way to make this change for a company-managed business projects is by creating a new status with the new name.

            It is imperative that Atlassian reconsider the implementation of this feature as most customers cannot use company-managed business projects in the current scenario.

            Rodolfo Romero - Adaptavist added a comment - These are some of the reasons why we need this feature to be added to company-managed business projects: Team-manage projects supports this feature. Company-manage software projects support this feature in Server and Cloud. If a project contains different workflows for different issues types, which is a very normal case in a company-managed project, only one workflow can be mapped to the board. How do we track the other workflows in the board? In the current situation, this is not possible. Migrations from Server/DC to Cloud are broken because business projects cannot be migrated to a Cloud company-managed business project that lacks of a feature that has always been there. In the current scenario, if a column needs to be renamed, the whole workflow needs to be modified as changing the name of a status in the existing workflow will impact globally other workflows in the system. This means that the only way to make this change for a company-managed business projects is by creating a new status with the new name. It is imperative that Atlassian reconsider the implementation of this feature as most customers cannot use company-managed business projects in the current scenario.

              Unassigned Unassigned
              ovargas@atlassian.com Omar Vargas
              Votes:
              15 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: