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

Please remove message "The Classic boards are no longer being actively improved ..."

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • 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.

      Lately, JIRA users are confronted with this message:

      "The Classic boards are no longer being actively improved and are not recommended for use in new projects. Learn more about Getting Started with the new boards."

      This is very irritating for our users, especially as they do not understand, what THEY should concretely do differently. when you have 2,000 users this is a real cost factor / waste.

      please remove the message.

            [JSWSERVER-6789] Please remove message "The Classic boards are no longer being actively improved ..."

            Martin (Inactive) added a comment -

            Hi everyone,

            I have closed this issue as Won't Fix. Please see The Future of Agile for further details of the removal of Classic boards from JIRA Agile.

            Kind regards,
            Martin
            JIRA Agile

            Martin (Inactive) added a comment - Hi everyone, I have closed this issue as Won't Fix. Please see The Future of Agile for further details of the removal of Classic boards from JIRA Agile. Kind regards, Martin JIRA Agile

            Shaun Clowes (Inactive) added a comment -

            Hi everyone,

            Thanks so much for your votes and comments on this feature request.

            We know there are features missing from the new Scrum and Kanban boards. We believe that this feature request is a band aid solution to those missing features. We believe that this feature would take time and energy away from us making the new boards even better.

            While we understand the desire for this feature it will add complexity to the product and hinder adoption by new teams. Complexity of the user interface due to configuration options is the most common complaint we receive from customers, and our continued goal is to make GreenHopper easier for teams to adopt. Further, adding this option adds to the ongoing cost of testing and maintenance, which hiders the teams velocity over the long term.

            As we continue work on delivering many new features in GreenHopper there are a few options open to you. You can start switching individual teams over to the new boards as they complete their current sprint, project or release. Alternatively, you can continue to use the Planning, Task, Chart and Released Boards and the current functionality by remaining on GreenHopper 5.10.6 and JIRA 5.1.2 , or by using the 'Classic...' option under the Agile menu in GreenHopper 6.0 or later.

            Just like any Agile team we have ordered the backlog based upon what we believe provides the greatest value to our customers. There are now over 10,000 customers worldwide so we try to find the right balance between the varied needs of this large, and growing, group. It is not an easy task. Thankfully we have many passionate customers that are able to provide feedback to help drive our vision and order the backlog - thank you!

            Thanks for your patience, and we hope you appreciate our open approach to feature requests and backlog ordering.

            Cheers,
            Shaun Clowes
            GreenHopper Product Manager

            Shaun Clowes (Inactive) added a comment - Hi everyone, Thanks so much for your votes and comments on this feature request. We know there are features missing from the new Scrum and Kanban boards. We believe that this feature request is a band aid solution to those missing features. We believe that this feature would take time and energy away from us making the new boards even better. While we understand the desire for this feature it will add complexity to the product and hinder adoption by new teams. Complexity of the user interface due to configuration options is the most common complaint we receive from customers, and our continued goal is to make GreenHopper easier for teams to adopt. Further, adding this option adds to the ongoing cost of testing and maintenance, which hiders the teams velocity over the long term. As we continue work on delivering many new features in GreenHopper there are a few options open to you. You can start switching individual teams over to the new boards as they complete their current sprint, project or release. Alternatively, you can continue to use the Planning, Task, Chart and Released Boards and the current functionality by remaining on GreenHopper 5.10.6 and JIRA 5.1.2 , or by using the 'Classic...' option under the Agile menu in GreenHopper 6.0 or later. Just like any Agile team we have ordered the backlog based upon what we believe provides the greatest value to our customers. There are now over 10,000 customers worldwide so we try to find the right balance between the varied needs of this large, and growing, group. It is not an easy task. Thankfully we have many passionate customers that are able to provide feedback to help drive our vision and order the backlog - thank you! Thanks for your patience, and we hope you appreciate our open approach to feature requests and backlog ordering. Cheers, Shaun Clowes GreenHopper Product Manager

              Unassigned Unassigned
              e38d6709d13b rainer mueck
              Votes:
              7 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: