Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-91112

Card colors for issuetypes not configurable when issues are not present on the project

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

      Problem

      Card colors not available for issue types for project when issues are not present for that particular issue type for the project (Scrum Board)

      Environment

      JS

      Steps to Reproduce

      Create a scrum board for a new company managed project
      Go to Board settings > Card colors > Select Colors based on issue types
      You will see that the issuetypes are not loaded

      Expected Results

      The card colors for issuetypes should be available for editing as the assignee, priorities and queries are available for editing.

      Actual Results

      The card colors for issuetypes are not available for editing

      Workaround

      create an issue with type - story in your project and the card colors for issue types story is available for editing. create an issue for the issue types required to be displayed here.

      Notes

            [JRACLOUD-91112] Card colors for issuetypes not configurable when issues are not present on the project

            Atlassian Update - March 24, 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 prioritize 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 (no votes or comments 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 in https://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!

            Matthew Hunter added a comment - Atlassian Update - March 24, 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 prioritize 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 (no votes or comments 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 in https://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!

              Unassigned Unassigned
              d31ee7a4b64e Aruna Johny (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: