• 1
    • 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 the company managed project, while viewing the Roadmap , Status name for issue is not fully displayed.When we resize the roadmap width, still can't see the full status name .

      If we have statuses with similar names and it is impossible to understand what status the issue has at the moment:

      • Ready for Development and Ready for Design
      • Design and Design Review

      Even when hovering, the full name of the status does not appear, you have to click on each issue to check the status.

      Is there a way to fix it?

            [JRACLOUD-91592] Complete Status name in Roadmap view

            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

            A work around was suggested to me by Atlassian support:

            Alternative workaround

            1. There is a marketplace plugin known as New Status Colors PRO for Jira Cloud that can help to customize different colors for each status and it might be easier for you to differentiate the READY FOR DEV and READY FOR TEST.
            1. You can download this app from this link and the instructions are listed here

            The workaround suggested is not an option at the price being charged!

            Atlassian we just want these issues addressed! Not much to ask!

            Adam Buckingham added a comment - A work around was suggested to me by Atlassian support: Alternative workaround There is a marketplace plugin known as New Status Colors PRO for Jira Cloud that can help to customize different colors for each status and it might be easier for you to differentiate the READY FOR DEV and READY FOR TEST. You can download this app from this link and the instructions are listed here The workaround suggested is not an option at the price being charged! Atlassian we just want these issues addressed! Not much to ask!

              Unassigned Unassigned
              861e4011cf01 Prerna Sony (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: