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

(info) Note that this page only applies if you are using the Classic Boards (which are no longer being actively developed; read more).

You can schedule and assign issues with ease in GreenHopper. By dragging and dropping the cards on the Classic Planning Board, you can associate your issues with a (Fix for) Version, Component or Assignee.

To schedule or assign an issue in GreenHopper Classic,

  1. Log into JIRA.
  2. Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
  3. Select your project from the project dropdown in the top navigation bar, if it is not already selected.
  4. Change the Planning Board mode to categorise your issues by versions, components or assignees.
  5. Select one or multiple issues (i.e. cards) with your mouse.
    • If you are using the 'Cards' or 'Summaries' viewing mode, click the 'header' of each card (i.e. the top section of the card, containing the issue key).
    • If you are using the 'List' viewing mode, click the coloured vertical bar at the far left of the row.
  6. To select a single card, just click the desired card.
    To select multiple issues, you can do either of the following:
    • Selecting multiple ungrouped cards (i.e. cards that are not adjacent to each other) — Hold down 'CTRL' on your keyboard and click to select the desired cards.
    • Selecting multiple grouped cards (i.e. cards adjacent to each other) — Click a card, hold down 'SHIFT' on your keyboard and click another card above or below the first one (or two or more cards to the left or right of the first). All cards between and including the cards you clicked will be selected.

    (tick) Tip: If you hold down 'SHIFT' on your keyboard and click an issue, without clicking a card first, then all issues from the top of the Planning Board down to the clicked issue will be selected.

  7. Drag and drop the selected card(s) to the version/component/assignee box with which you want to associate the issue(s).
    • If your issue(s) have sub-tasks, you will also be promped as to whether you want to schedule/assign each of the sub-tasks along with the parent issue. Select the sub-tasks to schedule/assign and click the Update button.
  8. GreenHopper will schedule/assign the issues immediately, as well as update the statistics on the boxes on your Planning Board.

(tick) Tip: You can also move sub-tasks from one issue to another by dragging and dropping the sub-task card(s) to the desired issue.

(info) Note:

  • You will need the 'Edit Issues' and the 'Schedule Issues' permission issues in order to move issues to a different version on the Planning Board. Additionally, depending on the 'Scheduling Permission' setting in your GreenHopper General Configuration, you may also need the 'Resolve Issues'  permission. (Note that the 'Schedule Issues' permission is always required, regardless of the Scheduling Permission setting in GreenHopper General Configuration.)
  • You will need the 'Edit Issues' and the 'Assign Issues' permission in order to re-assign issues.

 

Screenshot: Dragging a card to a version box

 

 

 

  • No labels

23 Comments

  1. Darshak Thakore

    is it possible to assign an issue to multiple versions in greenhopper?

    currently it seems if i have an issue assigned to one fix version and if i also want to assign it to another fix version, greenhopper will not do it for me

    1. Nicholas Muldoon [Atlassian]

      Hi Darshak,

      That is correct. In GreenHopper an issue can only be found within one version. We will correct this deficiency in a future release, keep an eye on GHS-945 for more information on this issue.

      Thank you.

      Nicholas Muldoon

      1. Anonymous

        Hi Nicholas. I'm confused by your answer here. If I have an issue applied to two fix versions and use drag and drop to apply it to another I lose my two originals. GHS-945 will not fix this?. The Rapid planning board does not look like it will function in this way so cannot solve it even with a Sprint field. If there is not already a GHS for this issue can you please create one. Thanks

  2. Anonymous

    How do I limit the list of assignees on right side of Planning Board to only include my project team ? Currently there are 800+ people on that list which basically makes it impossible to assign the issue to a person with Planning Board.

    BR; Kari

    1. Nicholas Muldoon [Atlassian]

      Hello,

      Please use the Project Roles feature. You can find this in your project administration. Simply specify the developers in your team and they will be the only people shown in your dropdown.

      Thank you,
      Nicholas Muldoon

      1. Anonymous

        Hi,

        We have our roles specified and users listed for those roles but the dropdown still have hundreds of people in it.   Anything else I need to do make just our team show up in the Assignee dropdown?

        1. Anonymous

          Nevermind, figured it out.  Removed the "group" that was listed and that shortened the list

  3. Anonymous

    I understand scheduling to mean setting the order of issues to be addressed or tasks to be done, but this doesnt address this meaning of scheduling, and I cannot find anything in the rest of the documentation to explain it.

    eg when I look in the planning board I want to see issues in the order that I want them tackled. In the Task View I wnat to see them similarly, but somehow some issues are listed at the top and some under 'other issues' - to me scheduling means changing that order and I cannot find any way of doing this.

    Also I cannot find any documentation to explain how Greenhopper decides on the task list order

    (ps I would log in but my login gets rejected - I have a login for my projects, seemingly I needed a second login to be able to post issues to the help desk, does this mean I need a third login to comment on help docs (and if so, how many other logins will I need, and for what?)

    1. Nicholas Muldoon [Atlassian]

      Hello,

      It sounds like you may wish to use the Compact view for the Task Board. You can change this under the View menu in the top right.

      The Outline view, which you are using today, lists the sub-tasks below their parent on the Task Board.

      As for scheduling, this is done using the ranking. If you are a kanban team then the engineers will just pull from the top of the ready for development queue. If you are a scrum team then you will use the Markers (find them via the Statistics button above the Versions on the Planning Board) to help schedule work into sprints.

      Logins - we've got a tonne of them. It is a historical problem that we're slowly working to address. You will need another login to post here in the interim. Thanks for your patience with all the username/password combinations (we use 1Password internally if that helps).

      Thank you.
      Nicholas Muldoon

  4. Matt Robbins

    I have a project that I have enabled Greenhopper for but when I try to drag and drop the issue to the different Version they don't get assigned. They just snap back in place. What am I missing to allow this to happen?

    Thanks,

    Matt

    1. Nicholas Muldoon [Atlassian]

      Hi Matt,

      Please ensure that you have the Schedule Issues permission.

      Thank you.
      Nicholas

      1. Matt Robbins

        Thanks Nicholas.

        I checked that and made sure they had Clsoing an issue and it works now.

        Thanks so much for your help.

        Matt

  5. Anonymous

    Hello,

    our reality is that we need to handle different products /projects within the same Sprint.

    I want to have a planned Sprint in Greenhopper including issues from different projects (products). How can it be organized?

    Thank you for your reply.

     

    1. Nicholas Muldoon [Atlassian]

      Hello,

      As you are looking for support for multiple JIRA projects you may wish to explore the Rapid Board.

      Thank you.

      Nicholas Muldoon

  6. Matt Harris

    I am unable to assign issues to a user.  I am listed as an administrator, but when I start typing the users name, there is no list for me.  I am able to perform this from within Jira however.  I have tried even adding myself individually to assign issues in the administration, but it is still not working.

    1. Rosie Jameson [Atlassian]

      Can you please check that the one or more people in your project have the "Assignable Users" permission?

      If that's not the problem, then please contact Support for assistance: http://support.atlassian.com — many thanks.

  7. Anonymous

    I'm looking for some help with further filtering our "Assignable Users" list. We have developers, who of course should show up in Greenhopper. We also have a large set of what I will call "Contributors." These include QA staff, Business Analysts, etc. who may be assigned issues in order to answer questions, elaborate on requirements, etc. I'd like to omit these users from the asignee view in Greenhopper. I don't need to manage these users' workload and having them in the list makes it harder to get a clear view of my team. Any suggestions?

    1. Nicholas Muldoon [Atlassian]

      Hello,

      You can set the Project Roles to specify who will show up in the Assignees list. Only those people in the Developers Project Role will be assignees. 

      Thanks,

      Nicholas

      1. Anonymous

        Thanks for the reply!

        However, I can't get that to work. I created a new role called "Contributors," with exactly the same permissions as "Developers" (including "Assignable User"). Then I moved all of my non-developer users to this role. I confirmed these changes on the "View Project Roles for User" screen. However, these users still appear in the Planning Board / Asignee View.

        Just want to make sure I understand whether this is working as designed, or whether this is a bug.

        Thanks again!

        Dan

        1. Nicholas Muldoon [Atlassian]

          Hi Dan,

          Sorry for leading you down the wrong path. As you want the Contributors to also be assignable - Assignable User permission (Users with this permission may be assigned to issues) - then they will show up in the Assignees drop down.

          There is no way to remove only some of the assignable users from the list.

          Apologies.

          Nick

  8. Gary Gregg

    I have a scenario where an issue is assigned to fix version 'A', and some work has been done and time logged against the issue however the issue is not complete and must be moved to fix version 'B'.  How can I split the issue so I can keep my work logged during fix version A on that versions time report and have work logged during version B on that report for the same issue?

     

    Thanks.

  9. Anonymous

    Hi,

    How can I assign multiple users to one task (for workshops, and so on) ?

  10. Laszlo Kremer

    The "Scheduling Permission" setting does not control anything. I have people in the "Schedule Issues" permission but not in the "Resolve Issues" permission. They can put tickets into versions regardless how the "Scheduling Permission" is set.

    I expect that when I unselect it, the guys who are not in the "Resolve Issues", will not be able to put tickets into versions.

    GreenHopper itself overrides the "set fixversion" permission without checking this checkbox.



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.