Search the GreenHopper 5.8.x Documentation:

Index
Downloads (PDF, HTML & XML formats)
Other versions

This documentation relates to GreenHopper 5.8.x.
If you are using an earlier version, please view the previous versions of the GreenHopper documentation and select the relevant version.
Skip to end of metadata
Go to start of metadata

GreenHopper allows you to set up rankings for your issues to help you organise tasks in your product/sprint backlog more effectively. Rankings allow you to prioritise issues at a more granular level than issue priorities in JIRA, as rankings can help you to determine whether a single issue is more important/urgent than another single issue. For example, you may have two separate issues which both have a priority of 'Major'. Using GreenHopper, you can assign one of the issues a higher ranking than the other.

 

To rank issues in GreenHopper,

  1. Log into JIRA.
  2. Click the 'Agile' link's down-arrow in the top navigation bar and select 'Planning Board' from the resulting dropdown menu. The 'Planning Board' will be displayed. (tick) Tip: The 'Project Overview' mode is ideal for ranking issues.
  3. Select a Context that is sorted by rank (e.g. look for a context named 'Rank'). If one does not exist, you can either create a new context or modify the 'On The Fly' context to sort by the 'Rank' field.
  4. Your issues will be ordered by rank.
    (info) Note that sub-tasks can only be ranked within the parent task.
  5. You can now rank your issues by dragging and dropping the cards on your Planning Board as desired see below.

(info) You need to set up a Ranking field before you can rank issues. Please see Configuring your General Project Settings for details.

 

Dragging and Dropping Cards

 

You can drag-and-drop one or multiple cards in GreenHopper with your mouse. Just hold down the 'CTRL' key on your keyboard (if selecting multiple issues), click the card header (i.e. the top section of the card, containing the issue key) to select the desired card(s), then drag to the desired destination.

Screenshot:Dragging and dropping a card

You can move an issue(s) between pages by dragging the card(s) up to the pagination controls (e.g. '1', '2', '3', '>>', etc) and then onto your chosen page in the desired location.

Once you have dropped a card in a new location, the other cards are immediately reorganised.

If you drag and drop an issue with sub-tasks, all of the sub-tasks will also be moved together with the parent issue. You cannot drag and drop a parent issue onto a subtask nor a subtask onto a different parent issue.

Labels:
  1. Jan 04, 2011

    Is there a way other than drag-and-drop to assign ranks to issues, such as editing the Rank field directly?

    I have many issues whose ranks need updating and drag-and-drop is inefficient. Some issues need to move from the top of the list to the bottom, requiring the window to scroll for several seconds while dragging.

    Ideally, I'd like the Rank field to be shown in the List view of the Planning Board. Normally I'd add it using the Card Styles configuration screen. But Rank does not show up in the list of available fields.  Is there another way to add it?

    1. Jan 23, 2011

      Hi Eva,

      Yes, you can edit the rank via the JIRA Edit Issue screen as an alternative to the drag and drop.

      One reason we have avoided displaying the rank field on the card itself is that the value of the field displayed is an 'absolute' rank while the data stored in the field is relative. As such, any update of the rank field on one card we would require a reload of all other cards, so that they could obtain their new 'absolute' rank value.

      Thank you Eva.

      Regards,
      Nicholas Muldoon

      1. Dec 16, 2011

        I can't seem to get the rank field to show in the JIRA edit issue screen even though the field has been added.

        Any special magic that needs to be performed ?
        The release notes seem to indicate that this is disabled and only drag&drop is supported in the GH UI....

        This is really annoying some of the people here, since they have to do prioritisation over 4000+ issues in some projects and drag & drop is not really an ideal solution to that (sad) 

        1. Jan 25, 2012

          Anonymous

          I don't see it either.  Is it supposed to be there or not?

          1. Jan 30, 2012

            Sorry, there is a problem with this at the moment – we are working on it.

            You may like to watch/vote on GHS-3967

  2. Jan 05, 2011

    I have exactly the same problem:

    The ranking field cannot be added to the templates and thus does not show in any of the views.

  3. Jan 20, 2011

    Anonymous

    Similar problem, except across pages.  I have not found a way other than 'edit' of the story to move one storte to the end of the list across multiple pages.  If I want to move the first 15 stories to the end of 200 stories, i have to edit 15 stories one by one.  If there is a better/faster way, please let me know as it would save a LOT of time.

    Thank you

    1. Jan 23, 2011

      A better way to do this is to select all cards, either with a Shift-select or a Control-select, and then drag them up to the pagination and to the final page.

      You can then drop the cards at the end of the last card, on the final page of the pagination.

      Thank you.

      Regards,
      Nicholas Muldoon

  4. Jan 20, 2011

    Anonymous

    I found I could use Preferences to select the number of cards on a page - which I increased to > than the number of assks that I had.  Then I did not have a page boundary to try to move rank across.

    thanks

  5. Feb 02, 2011

    Dragging and dropping between pages is not working for me.  I select a story on the third page, drag it to the page selecter until it opens up the pop-up with the page's stories, place the story I am dragging in the correct location on the new page and drop.  As soon as I do, poof, the story is back where it was before I started the drag and drop.  Is there some setting that I need to change?  I am able to change story ranking within a page, just not between pages.

    1. Feb 13, 2011

      Anonymous

      I'm having the same problem.  I changed my view to show more issues on a page hoping for a work-around.  No luck though.  I drag, drop, refresh and the issue jumps back to it's original location.  Anyone know of a work-around?

      1. Feb 14, 2011

        Hello,

        There is no setting that you need to change to get this to work. Can you please ensure that you are using the latest version of GreenHopper.

        If you are on the latest version of GreenHopper please raise a support request.

        Thank you.
        Nicholas

        1. Feb 14, 2011

          I found out what was wrong.  For some reason when I applied the Greenhopper project template to my new project it did not correctly set the Ranking field to Rank.  Rather it was not set at all.  I have since set the Ranking field to Rank and I am now able to rank my stories correctly.

          1. Feb 15, 2011

            Anonymous

            Seems to me if you were able to drag-and-drop on a single page, Rank must have been setup correctly.

            I am having the same problem: I can D&D within a page, but not across pages.

            Perhaps I'm not "aiming" for the right place.  Do you drag to:

            1. right on top of the destination page marker?

            2. Just a bit to its right?

            3. to the top of the large grey box that appears when you hover over a destination page?

            4. As above, but drop the source item somewhere within the large grey box?

            5.?

  6. Feb 14, 2011

    Anonymous

    One aspect I found that wasn't described above in the Important Information box above is that ranking only works if your context is set to sort by the rank field.

    I had set the sort order to be by Priority for temporary purposes, and then the Drag and Drop resort stopped working.

    1. Feb 15, 2011

      (Adding this reply just be shown as logged in (which I had forgotten to do above) and watch this page.)

  7. Feb 23, 2011

    I am wondering, why changing the rank is not reported in the history?!

    1. Feb 23, 2011

      Hi Marco,

      More discussion on the topic can be found here. In short, whenever you rank one issue it could change a relative rank on all other issues in the project, which would lead to a lot of noise and not much value (plus a large number of notification emails).

      Feel free to join the discussion on GHS-347

      Thanks,
      Nick

  8. Mar 17, 2011

    Anonymous

    Hi All,

    Am new to this GreenHopper in jira. Actually i have a associated the Rank Field to my Project and

    i have placed it on Create Screen of the Corresponding Issue Type.

    Question1: when i create the issue i got the Rank Field but the text at right of the Field displays

    as disabled?

    Question2: Can i pass any value into that field of create Screen or the plugin automatically set the

    Ranks for our issues?

    Question3: After i create an issue when i click on the planning board i see lot of cards where am

    unable to see any rank for the issues?

    Question4: On which Screen i have to place this Field?

    I think i have done correctly till associating the Rank Field with Project and issue type,after

    that what i have to do that am not aware please help me out......:(

    Thanks in advance.

    Nagul Shaik

    1. Mar 21, 2011

      Hi Nagul,

      You will need to ensure that the Rank custom field (of GreenHopper Ranking type) is available for all issue types in your JIRA Project. Please also ensure that you have the Context set to Sort By the same Rank custom field. Once you have done this the issues on the Planning and Task Boards are displayed in rank, sorted ascending.

      You can change the Rank field upon issue creation via the New Card dialog on the Agile tab. You will probably also want to add the Rank field to the Default screen.

      Thank you Nagul.

      Regards,
      Nicholas Muldoon

  9. Jun 14, 2011

    Anonymous

    Hi,

    I'm working on an customizedView by making a xml-export and embedding xsl. Which format do CustomFields of type "Rank" have? 

    For example i get "5.5e8" for a value in htmlview of "54"...

    or in which table is "rank" saved? there is no entry in "customfield"-table.

    thx in advance

  10. Jul 13, 2011

    In case this helps anyone:

    I have a scenario where a single "DEV" JIRA Project has multiple backlogs within it based on different saved filters with Component restrictions. Also, I wanted to keep track of the top requests from each department, which often cross the product backlogs. I was able to do this in the following way:

    • In addition to Rank, I created a second GH Ranking field called "Team Rank" (dept. rank) and added that to the rank fields for the project.
    • I created a bunch of JIRA query filters called things like "Document Management Backlog" (a product backlog) and "Accounting Team Backlog" (a dept. backlog).
    • I created a shared GH context of the same name for each filter. For the team ones, I chose to sort by Team Rank, and for the product ones I sorted by Rank.
    • I have confirmed that I can now maintain all my product backlogs in one JIRA project, and also store my top requests per team using the dept/team rankings. Drag-ranking things in a Team Rank context doesn't mess up the Rank and vice versa.

    It's a bit of an odd setup but it works for us. We don't really publish versioned products - instead we are an internal dev team who does tons of ad hoc reports, intranet pages, tools, etc. We just have sprints marked 2011.7.1, 2011.7.2 etc. (first and 2nd sprints of July 2011) and we drag a mess of stuff in there.

    Hope this may help someone.

  11. Jul 26, 2011

    Hi I have developed a UI to interact with the JIRA SOAP API. I have successfully changed the ranking value, yet I could only change the "absolute" value of the ranking, which often leads to a wrong "relative" ranking (which Greenhopper actually shows). Does anyone know the ranking mechanism that Greenhopper uses?

    Is it allowed for me to edit the rankings for all the issues in my project and then upload them all at once?

    1. Jul 27, 2011

      Hi Michael,

      It is a bit of a black box at the moment. Best bet, raise a feature request for the ability to update the rank field via an interface.

      We'll likely do this via a Java and REST API for the Global Rank field closer to December. Note, the Global Rank field is only used on the Rapid Board and we'll be migrating the GreenHopper Rank custom field to this.

      Thanks Michael,
      Nicholas Muldoon

  12. Jul 28, 2011

    The Greenhopper Ranking field is not supported by Athlassian.

    1. Aug 17, 2011

      Hi Michael,

      The GreenHopper Ranking custom field is supported by Atlassian, it is a core component of GreenHopper which is a supported product.

      Did you have difficulty getting support for its configuration or usage? If so please let me know.

      Regards,
      Nicholas Muldoon

      Skype: nickmuldoon
      Twitter: @nickmuldoon

  13. Aug 31, 2011

    In general, the newest things are the most important things for us.  Is there any way that the default rank could be at the top of the list instead of last?

    1. Dec 22, 2011

      Anonymous

      +1 for this

  14. Sep 11, 2011

    Hello,

    What is the best practice for ranking issues? We have difficulties to rank unscheduled issues. We prepare in front always a release and some sprints and keep a lot of issues unscheduled. Different users can add new stories, epics...

    However, moving (drag & drop) is taking some time and as requests, priorities...changes very often, it's very difficult to keep the unscheduled issues with a proper ranking.

    We use some custom fields in order to identify some priority aspects of our issues like:

    • User value is simply the potential value of the feature in the eyes of the user. Product managers often have a good sense of the relative value of a feature, ("they prefer this over that") even when it is impossible to determine the absolute value. And since we are prioritizing like things, relative user value is all we need.
    • Time value is another relative estimate; one based on how the user value decays over time. Many features provide higher value when they are delivered early, and differentiated in the market, and lower value as features become commoditized. In some cases time value is modest at best ("implement the new UI standard with new corporate branding"). In other case, time value is extreme ("implement targeting criteria before September"), and of course there are in between cases as well (support Internet Explorer browser).
    • Information discovery value adds a final dimension – one that acknowledges that what we are really doing is software research and development. Our world is laden with both risk and opportunity. Some features are more or less valuable to us based on how they help us unlock these mysteries, mitigate risk, and help us exploit new opportunities. For example, "move user authentication to a new web service", could be a risky effort for a shrink-wrapped software provider that has done nothing like that in the past, but imagine the opportunities that such a new feature could engender.

    Each of those priorities have a value from 1-10. Finaly, taking into aspect the story points we obtain [(user value + time value + IDV) / story points] = Weighted shorted jobs First (SWJF) which is in fact an "objective ranking" of the issues (but some issues can have the same value).

    My question:  is it not possible to rank issues based on a filter [Defining an order based on whatever criteria (e.g: order by WSJF or any custom field)]?

    The purpose would be, that the project manager could apply an automatic ranking based on a defined filter.  After this ranking, the project manager could still change the ranking based on subjective criteria (drag & drop) and chose whenever he wants to reset the ranking based on a filter.

    Does this kind of functionality already exist or is there some work around or is this a feature request? This would help us (as project manager) numerous hours of planning, adjusting... and still have the flexibility of manually adapt the ranking if necessary.

    Many thanks for you feedback.

    Kind regards,

    JJ Courtens
    Adlogix
    skype: jjcourtens71

    1. Sep 14, 2011

      Anonymous

      I have the same question/request. Using JIRAs filter to assign ranks is the most wanted feature for GreenHopper ranking system.

      Looking forward for the answer.

       

      Vadim Goryunov

    2. Sep 23, 2011

      Anonymous

      Hi. same issue here. I have a JIRA query by priority and a few other fields that i want to use as the base rank, then manually triage.

  15. Sep 11, 2011

    By the way, we're using JIRA studio

    Thx,

    JJ

  16. Oct 11, 2011

    Anonymous

    Is there a way to limit the rights to force rank in Unscheduled/Product Backlog bucket to Product Manager role only?

  17. Oct 18, 2011

    Anonymous

  18. Oct 25, 2011

    Anonymous

    Hi,

    I noticed that only issues that have sub-tasks are correctly ranked on a Task Board. On planning board issues are sorted in a right way (according to set rank), but on the task board issues with no sub-tasks go to "other issues" tab. Is it a known bug?

    1. Oct 25, 2011

      Hello,

      It sounds like you have the Outline Mode enabled on the Task Board. You may wish to switch to the Compact (Kanban) Mode. More information can be found on Using the task board modes.

      Thank you.

      Nicholas

  19. Nov 03, 2011

    Anonymous

    What is the difference between Rank and Global Rank?

    1. Nov 03, 2011

      "Global Rank" is a new type of custom field which was introduced in GreenHopper 5.8 (for details, please see the GreenHopper 5.8 Upgrade Notes).

      1. Nov 04, 2011

        Anonymous

        Is there a way to get 1) the relative ranking of the current open issues.  2) the relative ranking within a fixVersion (sprint)?

        1. Nov 06, 2011

          Hello,

          You will see the relative ranking of the issues within your project on the Planning Board, to see all issues use the Project Overview mode.

          To see the relative ranking of only those issues within a Fix Version please switch to the Version mode on the Planning Board and then select your desired version.

          Thank you.

          Nicholas Muldoon

  20. Nov 07, 2011

    Anonymous

    Not sure if this is the right place for this - is there any way for new stories that are created to be prioritised highest instead of lowest? In our environment there are multiple people who capture stories and this would force the PO to see them and push them down explicitly rather than not seeing them at all...

    1. Nov 08, 2011

      Hello,

      I believe the functionality you are looking for is covered in this story. Please view, vote and comment on that issue to show your support.

      It is not on the backlog at present.

       

      Thank you,

      Nicholas

  21. Nov 23, 2011

    Anonymous

    Hi,

    I have a problem regarding the rank-field (I think). When first creating a story within my project, I get the Rank-field alright and are able to create the story. When I later try to view my story in Task Board, I receive the following exception:

    org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getPagination' in class com.pyxis.greenhopper.jira.boards.VersionBoard threw exception class java.lang.NullPointerException

    The story has then disappeared from the Planning Board and are categorized as an "other issue". The only way to see my story after this point is within the regular issue context (non-greenhopper), and when I try to edit my issue here I receive the following exception:

    java.lang.RuntimeException: Issue Ranking Operation log entry found where none expected. Please restart JIRA.

    The issue is also undeletable at this point (will confirm deletion, but won't actually delete the issue).

    Any suggestions what to do or directions to correct and faulty configuration regarding Greenhopper/Rank-field?

    Thanks!

    1. Nov 27, 2011

      Hello,

      Please raise a support request for assistance with this issue.

      Thank you,
      Nicholas Muldoon 

  22. Nov 28, 2011

    Anonymous

    For anyone lost like me - set your ranking field using these instructions.

    1. Nov 28, 2011

      Thanks - I've updated the page to include a link.

  23. Dec 11, 2011

    Anonymous

    As a Jira / Greenhopper Admin I should be able to veiw the 'Add Global Rank' button. But When I try to :-

    Enabling Drag-and-Drop Ranking

    To enable ranking of issues by drag-and-drop, and grouping of sub-tasks under their parent issue:

    1. Access the Rapid View Configuration for your Rapid View (see above), then click the 'Filter tab.

    Click the 'Add Global Rank' button

    I do not see "Add Global Rank" button !! 

    What could be the cause ? 

    Screen Shot - https://picasaweb.google.com/111990409777684508952/December112011?authkey=Gv1sRgCN_O76aTgZTrEg 

    1. Dec 12, 2011

      Can you please advise which version of GreenHopper you are using? Also, did you upgrade from a previous version and if so, did you have a Ranking field configured prior to the upgrade?

      Many thanks

      1. Dec 12, 2011

        Anonymous

        We are using GreenHopper- 5.7.  Yes we did have the ranking feild enabled prior to configuring the upgrade. Currently I can see the new "Global Rank" feild but unable to edit it. 

        I can view the "Global Rank" feild on the ticket but am not sure where to go to edit it. Also when I try to re-prioritize tickes on the rapid board I am only able to move the tickets from one swim lane to another and am unable to prioritize the tickets. 

        1. Dec 12, 2011

          Hello,

          Can you please upgrade to GreenHopper 5.8, that will allow you to take advantage of the new Global Rank functionality.

          Thank you,
          Nicholas Muldoon 

          1. Jan 03, 2012

            Anonymous

            Hi - we are a bit confused by this change to ranking.  In our dev environments our rank field disappeared with the 5.8 upgrade so we have postponed the upgrade until we better understand how to proceed.  We often edited that field in Jira - especially on initial issue creation.  We would also reference it and sort by it in the issue navigator as a guide for bulk edits, updates etc. We would rank in Greenhopper as more "fine tuning" but initial rank we set at issue creation time with the rank field.  Is this no long possible?  If so I don't understand the rationale - we found the rank field very useful.

            1. Jan 09, 2012

              Hello,

              A bit of background, we changed the ranking functionality from being per-project to global to enable teams to plan and rank stories across multiple projects.

              In doing this we removed the ability to edit the rank on the JIRA View / Edit Issue screen as it no longer made sense - ie, you were no longer ranking within a project, you were ranking within the global context in JIRA. Instead, the way to rank issues is in GreenHopper using the drag and drop or keyboard shortcuts in your selected Rapid View (Rapid Board) or Project/Context (Planning Board).

              When creating the issues via GreenHopper (using the 'c' keyboard shortcut for instance) you can set the initial rank of the issue you are creating. You can also still sort by the rank field on the Issue Navigator.

              More information on the future direction of GreenHopper can be found on The Future of GreenHopper page. A discussion about the ability to edit the rank via the JIRA Edit Issue screen can be found here.

              Thank you,

              Nicholas

  24. Dec 14, 2011

    As a project manager, I have a developer working on issues within two different Jira projects, Project A and Project B. I have used Greenhopper to rank all issues assigned to this developer within each project, so that he knows which issues to work on first relative to other issues within that project.

    However, the developer still does not which issue to work on first: the top-ranked issue from Project A or the top-ranked issue from Project B.

    What I need is a way to rank issues globally, across all Jira projects. So the project manager can rank issues within a project, but then rank all issues across all projects as well. That way, as a developer, I can login to Jira, see my dashboard, and know exactly which issue to work on first regardless of project.

    Does Greenhopper support global rankings in any way?

  25. Feb 10, 2012

    All my users seem to have the ability to adjust rankings. How can I restrict the ability to drag and drop so that only the admin can do it?

    1. Feb 10, 2012

      Hi Stephanie,

      By default the Resolve Issue Permission is used when identifying those users who can rank issue. You can change this to the Schedule Issue Permission if you wish.

      Thank you,

      Nicholas