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

Status customization in the board

XMLWordPrintable

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

      In team-managed business projects, the only way to add multiple "done" and "to do" statuses is through the workflow editor which is only accessible by going to the issue type configuration in project settings.

      New statuses added directly to the board are added as "In progress", it would be helpful if the status category can be changed while creating it on the board.

        1. screenshot-1.png
          screenshot-1.png
          49 kB

            [JWMCLOUD-518] Status customization in the board

            Matthew Hunter added a comment -
            Atlassian Update - October 31, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Matthew Hunter added a comment - Atlassian Update - October 31, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            IT Service Account added a comment -

            This would be super helpful in empowering our teams to self-support their projects so Jira Admins don't have to do it. It isn't intuitive to have to go into Issue Types (even though workflows are tied to Issue Types). Please and thank you!

            IT Service Account added a comment - This would be super helpful in empowering our teams to self-support their projects so Jira Admins don't have to do it. It isn't intuitive to have to go into Issue Types (even though workflows are tied to Issue Types). Please and thank you!

              Unassigned Unassigned
              gsandoval@atlassian.com Gino S
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: