Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

JIRA workflow statuses map to columns on a board.

(info) To configure these mappings, see Configuring Columns.

To transition an issue to a different JIRA workflow status on a board:

  1. Click the Agile link's down-arrow in the top navigation bar, then select your preferred board from the resulting dropdown menu.
  2. In 'Work' mode, transition an issue (or issues) by dragging and dropping the issue from one column to another (see  Screenshot 1 below).

    • Use <Ctrl> or <Shift> to select multiple issues.
      (info) It is currently not possible to transition multiple issues by dragging them to another column. It is possible to move multiple issues within the same column.

    • When you start dragging an issue, you can only transition the issue to columns whose background turns blue. When the issue is hovered over the target column, the blue background turns green.
    • If the target column is associated with more than one status then, when the issue is hovered over that column, each status will appear as a separate section with a dashed outline (see Screenshot 2 below). Complete the transition to the appropriate status by dropping the issue onto the section of the column.
  3. If a dialog box opens for your workflow transition status, you must complete all mandatory fields (indicated by a red asterisk) before submitting the form.

(tick) You can also transition an issue via Keyboard Shortcuts if you prefer.

Related pages:

(info) Please note:

  • To map JIRA workflow statuses to columns in a board, see Configuring Columns.
  • You can only transition an issue if you have permission to move that issue to the status in the JIRA workflow to which the column is mapped.
  • GreenHopper will respect your JIRA worklow configuration and will trigger all your JIRA workflow validations, conditions, functions and notifications on the transitions. (See Configuring Workflow.)
  • Unlike the Task Board, the board currently does not auto-assign issues to you.
  • Once all the sub-tasks of an issue have been completed, it's time to resolve the issue itself. So when you move the last sub-task to the 'Done' column, GreenHopper will prompt you to move the parent issue too. If you resolved the sub-tasks in native JIRA instead, a button will be displayed on the parent issue the next time you visit Work mode.



Screenshot 1: Dragging and Dropping an Issue to Another Column


Screenshot 2: Dragging and Dropping an Issue to a Column with Multiple Statuses

34 Comments

  1. Ian Tyrrell

    Does the Rapid Board respect transition views/screens?

    I'm trying to get a screen (Resolve Issue) displaying when a user drags an issue to the done column but can't seem to get it to work - could just be a misconfiguration.

    1. Ian Tyrrell

      Please ignore - it was just a mis-configuration.

  2. Muhammad Rehman Khan

    Hi,

    I created my first sprint in JIRA and I am unable to move an issue from To Do to In Progress!!!

    Whereas I can drag it from To Do to Done???

    Please help!!!

    Regards,

    rk

     

    1. Nicholas Muldoon [Atlassian]

      Hello,

      It sounds like you may have a condition on your JIRA Workflow that only allows the assignee of the issue to move it to In Progress. Please check your workflow and consider removing that condition.

      Thank you,

      Nicholas

      1. Anonymous

        I had this problem and it was, in fact, because the default workflow only allows the assignee of a sub-task to move it into "In Progress."  Because you cannot edit the default I had to make a new Workflow, then a new Workflow Scheme, and then associate that with my project. Fortunately, all those steps are documented so it wasn't too hard.

  3. Edwin Stol

    Please note:

    To map JIRA workflow statuses to columns in a Rapid Board, see Configuring Columns.
    You can only transition an issue if you have permission to move that issue to the status in the JIRA workflow to which the column is mapped.
    GreenHopper will respect your JIRA worklow configuration and will trigger all your JIRA workflow validations, conditions, functions and notifications on the transitions. (See Configuring Workflow.)
    Unlike the Task Board, the Rapid Board currently does not auto-assign issues to you.
    Once all the sub-tasks of an issue have been completed, it's time to resolve the issue itself. So when you move the last sub-task to the 'Done' column, GreenHopper will prompt you to move the parent issue too. If you resolved the sub-tasks in native JIRA instead, a button will be displayed on the parent issue the next time you visit Work mode.

     

    My users are missing this feature, so i've browsed the public tracker and found this.
    Since the issue was lacking an Atlassian reply(not a bad thing, just a conclusion), it leaves me to wonder:is auto-assigning something for the short-term roadmap, long-term roadmap or maybe not even at all?

     

    1. Álvaro Sánchez-Mariscal

      Auto-assing feature is really important for most of the people.

       

      1. Anonymous

        Sounds painful.

  4. Anonymous

    We're using the Kanban rapid boards with our swimlanes set to the assignee.  Transitioning an assigned issue is working fine, and we just enabled ranking as well, but it would be great to be able to re-assign an issue simply by dragging it to another swimlane.  This would support the recommended Kanban workflow of taking the top-ranked un-assigned issue and putting it in your queue.

    1. Rosie Jameson [Atlassian]

      Thanks for this feedback. You may like to comment and/or vote on GHS-4518 - Getting issue details... STATUS

       

      1. Zach Leber

        Thanks Rosie, I've now created a login so I can do just that.

  5. Dave Scheet

    Relatively new to greenhopper,  is there a way to have subtasks transition when the parent is moved?  would also like subtasks to be able to move separately.

     

    basically, when a parent is moved to "in progress" we would like to have all subtasks move as well

     

    1. james larkin

      Yes i have related questions which is: the Rapid Board allows a feature to be in 'Done', while subtasks are still incomplete  --is it possible to enforce a rule on the rapid board so that the parent cannot be done while children are still in progress?

      1. Edwin Stol

        AFAIK, you cannot do that (yet) in Rapid Board, but you could do that with a condition on the transition in JIRA.
         

        1. james larkin

           cheers Edwin. Problem i struck there was that in GH6, you cannot edit that GreenHopper workflow  --or at least, you edit it at your peril. 

  6. John Hermary

    Is there a way to automatically transition sub-tasks when a task is transitioned?

    I.e. Say I have a Task "Task-A" that has 2 subtasks "Sub-1" and "Sub-2".  When I transition Task-A from from To-Do to In Progress, Sub-1 and Sub-2 do not transition to In Progress - they stay in To-Do.  I would like them to automatically get transitioned along with Task-A.

    1. Rosie Jameson [Atlassian]

      Not at this time, sorry. You may like to vote/watch/comment on GHS-6062 - Getting issue details... STATUS

  7. mreynolds0404

    "Once all the sub-tasks of an issue have been completed, it's time to resolve the issue itself. So when you move the last sub-task to the 'Done' column, GreenHopper will prompt you to move the parent issue too. If you resolved the sub-tasks in native JIRA instead, a button will be displayed on the parent issue the next time you visit Work mode."  This does not work very well with my team's workflow.  The tasks of a story transition from "In Progress" directly to "Done" (the last column), but stories should transition to "Ready to Test' when all the tasks are done (stories are not done until they are accepted by QA).  Because of this, whenever a developer finishes the last task of a story, he or she gets an error popup: 

    Update Parent Issue

     

    All sub-tasks for parent issue XXX-YYY are now Done.

    However, the parent issue cannot be moved into the Done column as there are no matching transitions.

     

    Is there a way to configure GH/JIRA to transition the parent story to a different status/column or just turn off the attempt to automatically transition the parent?

     

    1. Anonymous

      Our company would like this workflow as well, as we do not always want things to be closed when the team is done with it.

    2. Rosie Jameson [Atlassian]

      Hi, you may like to watch/vote/comment on GHS-7025 - Getting issue details... STATUS

      1. boardtc

        Not having the ability to have this pop up dialog configurable toggled off is an oversight as it assumes a certain way of working. In the teams I have been involved with the Product Owner, nobody else, closes the story, so this pop up option is bogus and leads to problems. It should be configurable.

  8. Óskar Friðrik

    Hi hi,

    I have a Kanban board that has many projects and two different workflows. This means that the columns don't strictly map to the statuses. I would like to be able to transition an issue from one status to another within a column but it seems not to be an option. I don't see why this should not be possible.

    Am I missing something or is this how GH is meant to work?

    Regards,
    Óskar Friðrik

     

    1. Peter Hesseling

      Hi,

      I am running into the exact same issue. This is forcing me to create more columns than I would like.

      Can someone at Atlassian please comment on this?

      Kind Regards,

      Peter

  9. Anonymous

    Hi Please can you assist? I have a Story on my Board that has a sub-task. I can move the sub-task into In Progress but not the actual Story. The story itself is spread across the whole board. How can this be moved into In Progress?

    1. Rosie Jameson [Atlassian]

      Hi, can you please contact http://support.atlassian.com? Many thanks

      1. Anonymous

        I've only been able to move stories to in progress or other columns when they don't have sub-tasks. If they have child tickets such as sub-tasks, these stories behave differently because they all child tickets must be completed before the story can be considered done. Generally you'll see a button on the right hand labeled 'Moved to Done' and when selected it closes the story. (ie., WLO-250) 

  10. Anonymous

    My old workflow used to populate the Resolution field as well as the status field. Using the above method, only my status field is populated...how do i force the resolution to also get populated as i transitions the tickets?

  11. Mark

    When will it be possible to transition multiple issues by dragging them to another column?

  12. Timur Poperecinii

    I have GreenHopper 6.1 installed. 

    The problem is that users from jira-users group can move issue on a GreenHopper board (Simplified Workflow) while they do not have permissions for it.

    And actually I don't want them to have those permissions.

    What am I missing?

    1. Rosie Jameson [Atlassian]

      The Simplified Workflow deliberately does not have conditions which limit the ability to drag issues between statuses, as this does appear to be what a majority of people require by default.

      To restrict the ability to move issues between statuses, you will need to set up a JIRA workflow that has the "conditions" (i.e. restrictions) you require — please see the JIRA documentation for information about workflow conditions.

      You will then need to set up a GreenHopper board to use this particular JIRA workflow.

      Please contact http://support.atlassian.com for further assistance if needed – many thanks

  13. Angelo Gouvis

    Above it states: "It is currently not possible to transition multiple issues by dragging them to another column."

    Any plans for that to change anytime soon?  It would be incredibly handy to be able to drag multiple tickets from one column to another, esp. if they are related subtasks, etc.

    1. Rosie Jameson [Atlassian]

      You may like to watch/vote/comment on GHS-5847 - Getting issue details... STATUS

  14. Andrea Tanzer

    When you drag an issue to the DONE column you can choose to RESOLVE or CLOSE an issue. However, when an issue is resolved, how can i then close it via drag and drop?

    Both statuses are within one column and i can not drag to the same column. Do I miss something?

    1. Rosie Jameson [Atlassian]

      Correct, you cannot drag to the same column, sorry. You will need to close the issue (a quick way to do this is to type "." and use the popup menu)



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.