Documentation for GreenHopper 6.0.x. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.

What is GreenHopper Simplified Workflow?

Every board represents one or more projects, and every project uses either a JIRA Workflow or a GreenHopper Simplified Workflow to control the movement of issues from one status to another. The workflow determines which statuses are available.

If your project was created together with a board via the GreenHopper 'Getting Started' page, it will probably be using a GreenHopper Simplified Workflow. If your project was created via JIRA, it will be using a JIRA Workflow.

GreenHopper Simplified Workflow offers the following benefits:

GreenHopper Simplified WorkflowJIRA Workflow

Has three default steps: To Do, In Progress, Done.

Has more steps than are typically needed on a board (e.g. see the default JIRA workflow).
Allows issues to be dragged freely between columns.Has workflow "conditions" which prevent issues from being dragged freely between all columns.
Displays no screens on any transitions – all transitions will happen instantly. (Automatically sets a resolution of 'Done' when issues move into the 'Done' column.)Displays screens for Resolve Issue, Close Issue and Reopen Issue.
Can be edited from within GreenHopper (see Adding a new status on the Configuring Columns page), provided you have the 'Administer Projects' permission (for the one project that is on the board).

Can only be edited via JIRA (see Configuring Workflow), not from within GreenHopper.

(info) For details about steps, transitions and conditions, please see the JIRA documentation on Configuring Workflow.

On this page:

Related pages:

Switching to GreenHopper Simplified Workflow

If your project(s) are currently using JIRA workflow, you may want to switch to GreenHopper Simplified Workflow. You will then be able to easily add new statuses from within GreenHopper.

To switch to GreenHopper Simplified Workflow:

  1. (warning) Before you begin, please back up your JIRA data (see the JIRA documentation on Backing Up Data). Please note that switching to a GreenHopper Simplified Workflow will migrate all of the project's issues to the new workflow, which may take some time. (The project's original workflow and scheme not be changed, so any other projects using these will not be affected.)
  2. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.

  3. Click the Columns tab.

  4. Click the Simplify workflow button as shown in Screenshot 1 (below).
    (info) In some cases this button may not be available — please see Why can't I switch to GreenHopper Simplified Workflow? (below).

  5. Your project(s) will switch to use GreenHopper Simplified Workflow as shown in Screenshot 2 (below). The Add Status button will now be shown.

 

Screenshot 1: the 'board Configuration' screen ('Columns' tab) — this board is not using GreenHopper Simplified Workflow:

Screenshot 2: the 'board Configuration' screen ('Columns' tab) — this board is using GreenHopper Simplified Workflow:

How can I tell if my board is using GreenHopper Simplified Workflow?

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.

  2. Click the Columns tab. You will see either:

    • The following words: Using GreenHopper Simplified Workflow (see Screenshot 2 above)
      or

    • The Simplify workflow button (see Screenshot 1 above)
      or

    • The following words: GreenHopper Simplified Workflow unavailable (see explanation below)

 

Why can't I switch to GreenHopper Simplified Workflow?

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

 

  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.