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

XMLWordPrintable

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

          Form Name

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

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3067433 ] New: JAC Suggestion Workflow 3 [ 3659918 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2623614 ] New: JAC Suggestion Workflow [ 3067433 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2324502 ] New: Confluence Workflow - Public Facing v4 [ 2623614 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2042158 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2324502 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2030196 ] New: JIRA PM Feature Request Workflow v2 [ 2042158 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 737058 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2030196 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 448755 ] New: JIRA PM Feature Request Workflow v2 [ 737058 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Blocker [ 1 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            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

            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

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

                Created:
                Updated:
                Resolved: