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

As a JIRA system admin I want to decide, if the GreenHopper UI supports "Simplified Workflows" 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 worldwide.

      The feature "Simplified Workflows" (http://confluence.atlassian.com/display/GH/Using+GreenHopper+Simplified+Workflow) would break our complete process rules and reporting infrastructure. therefore we need to be sure, that GreenHopper remains fully functional and consistent without "Simplified Workflows".

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

            [JSWSERVER-6677] As a JIRA system admin I want to decide, if the GreenHopper UI supports "Simplified Workflows" or not

            Thanks to everyone for their interest in this issue.

            As Shaun explained in his previous comment, the reason we will not pursue this request is because it would add unnecessary complexity to the interface.

            We believe there is sufficient controls in place to disallow users from performing this function, as they must be a JIRA Administrator (global permission). Furthermore there is sufficient explanation in the wizard as to what the ramifications are of carrying out this action, as there are in the documentation.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Thanks to everyone for their interest in this issue. As Shaun explained in his previous comment, the reason we will not pursue this request is because it would add unnecessary complexity to the interface. We believe there is sufficient controls in place to disallow users from performing this function, as they must be a JIRA Administrator (global permission). Furthermore there is sufficient explanation in the wizard as to what the ramifications are of carrying out this action, as there are in the documentation. Regards, JIRA Agile Team

            @Holger Schimanski: thanks for the hint!

            But actually, that is not sufficient. Far too many users have and need this permission for other good reasons - and they should NOT be able to decide upon their individual workflows!

            @Tom Kotecki: could you please bind the feature "Simplified Workflows" to individual projects? Or define a dedicated JIRA Administrators global permission for it?

            Rainer Mueck added a comment - @Holger Schimanski: thanks for the hint! But actually, that is not sufficient. Far too many users have and need this permission for other good reasons - and they should NOT be able to decide upon their individual workflows! @Tom Kotecki: could you please bind the feature "Simplified Workflows" to individual projects? Or define a dedicated JIRA Administrators global permission for it?

            @Rainer Mueck: See my link to the Greenhopper online documentation.

            You will only be able to switch to GreenHopper Simplified Workflow if:

            • There is only one project being viewed by your board (to check this, look at the board's filter); and
            • That project uses a JIRA workflow scheme which only has one workflow for all issue types; and
            • Your workflow only uses Post Functions, Validators, and Conditions which are provided by Atlassian (not any which are provided by plugins); and
            • You have the 'JIRA Administrators' global permission; and
            • You are using JIRA version 5.0.4 or later (please see Supported Platforms).

            Holger Schimanski added a comment - @Rainer Mueck: See my link to the Greenhopper online documentation . You will only be able to switch to GreenHopper Simplified Workflow if: There is only one project being viewed by your board (to check this, look at the board's filter); and That project uses a JIRA workflow scheme which only has one workflow for all issue types; and Your workflow only uses Post Functions, Validators, and Conditions which are provided by Atlassian (not any which are provided by plugins); and You have the 'JIRA Administrators' global permission; and You are using JIRA version 5.0.4 or later (please see Supported Platforms).

            @Holger Schimanski: where exactly did you read that? Thanks!

            Rainer Mueck added a comment - @Holger Schimanski: where exactly did you read that? Thanks!

            Holger Schimanski added a comment - - edited

            I stumbled over this feature request and was thinking in the same direction. But because Greenhopper Simplified Workflow has to be assigned to a project by a JIRA Administrator this feature can easily be restricted in its usage. The project admins cannot decide on their own to use it.

            Holger Schimanski added a comment - - edited I stumbled over this feature request and was thinking in the same direction. But because Greenhopper Simplified Workflow has to be assigned to a project by a JIRA Administrator this feature can easily be restricted in its usage. The project admins cannot decide on their own to use it.

            Thanks for your explanation, Shaun!
            Though I wish to chime in with the others as this creates a whole mess in many our our customers' JIRA installations as well as in ours. So an option to just disable this (or disabeling it via Plugin module etc.) would be so helpfull.

            David Toussaint [Communardo] added a comment - Thanks for your explanation, Shaun! Though I wish to chime in with the others as this creates a whole mess in many our our customers' JIRA installations as well as in ours. So an option to just disable this (or disabeling it via Plugin module etc.) would be so helpfull.

            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

            In our very large instance with 2.000+ Scrum teams (Jira projects) we need the capability to have a clue what is open - in process - done in terms of reporting. To have a fully free form of workflow would confuse many teams. They would have double maintenace to maintain the "simplified" and the project workflow.

            Stefan Kalhofer added a comment - In our very large instance with 2.000+ Scrum teams (Jira projects) we need the capability to have a clue what is open - in process - done in terms of reporting. To have a fully free form of workflow would confuse many teams. They would have double maintenace to maintain the "simplified" and the project workflow.

            rainer: For templates - agree, but I think of that is a would be nice for future. Classic also had templates and we didn't use them for some reason (either low priority to implement, or difficulty in implementation - probably the former, but I can't remember).

            Mark Mielke added a comment - rainer: For templates - agree, but I think of that is a would be nice for future. Classic also had templates and we didn't use them for some reason (either low priority to implement, or difficulty in implementation - probably the former, but I can't remember).

            Once more many thanks for your supporting comment, Mark!

            the next topic for me is TEMPLATES. I want to avoid that everyone must create his or her own rapid board and must take care of card visualization and status/column mapping in the task board. there should be templates defined by the JIRA system admin that scrum masters can just reuse. like in GH classic ... in the best case a scrum master has to do NOTHING, if he just wants to have a rapid board for project XYZ. it just should be there in a default manner.

            do you agree on that as well Mark?

            kind regards – Rainer

            rainer mueck added a comment - Once more many thanks for your supporting comment, Mark! the next topic for me is TEMPLATES. I want to avoid that everyone must create his or her own rapid board and must take care of card visualization and status/column mapping in the task board. there should be templates defined by the JIRA system admin that scrum masters can just reuse. like in GH classic ... in the best case a scrum master has to do NOTHING, if he just wants to have a rapid board for project XYZ. it just should be there in a default manner. do you agree on that as well Mark? kind regards – Rainer

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

                Created:
                Updated:
                Resolved: