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

As a JIRA system admin I want to decide, if the GreenHopper UI supports Epics or not

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

      We have built up a hierachy of issues types "Feature", "User Story" and "Story Task" - with custom coding for automatic issue links, status synchronization, custom field inheritance, effort accumulation and reporting. 2,000 users wordwide.

      An issue type "Epic" would break our complete logic and infrastructure. therefore we need to be sure, that GreenHopper remains fully functional and consistent without issue type "Epic".

      The UI must not have any references to "Epic" in this case.

          Form Name

            [JSWSERVER-6626] As a JIRA system admin I want to decide, if the GreenHopper UI supports Epics or not

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3066517 ] New: JAC Suggestion Workflow 3 [ 3661130 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2625265 ] New: JAC Suggestion Workflow [ 3066517 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327338 ] New: Confluence Workflow - Public Facing v4 [ 2625265 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044170 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327338 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032353 ] New: JIRA PM Feature Request Workflow v2 [ 2044170 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736960 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032353 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 447901 ] New: JIRA PM Feature Request Workflow v2 [ 736960 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Blocker [ 1 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            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

            Question: "our most recent user survey" ... what does that refer to?

            rainer mueck added a comment - Question: "our most recent user survey" ... what does that refer to?

              Unassigned Unassigned
              e38d6709d13b rainer mueck
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: