Ranking Issues in GreenHopper Classic

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?

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.

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

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

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.

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.

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

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

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

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.

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?

The Greenhopper Ranking field is not supported by Athlassian.

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?

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

By the way, we're using JIRA studio

Thx,

JJ

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

This is explained in details at: http://www.greenpeppersoftware.com/site/posts/list/344.page

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?

What is the difference between Rank and Global Rank?

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

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!

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

Sorry I meant these instructions....

http://confluence.atlassian.com/display/GH/Configuring+your+General+Project+Settings

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 

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?

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?

I have enabled ranking and setup a ranking context to sort my issues on the agile planning board. That works fine and I can drag and drop cards. However, I would prefer to rank issues by versions. Is that possible? Here is my setup..

I use the versions functionality to define my sprints. I want to rank the issues within each sprint in an order of 1 - N...

version "Sprint 1" has 20 issues....would like those issues to have a ranking system of 1-20 (and allow drag and drop re-order of ranking). 

Hi, is there any possibility to load all issues from VersionBoard view SOAP? Thanks.

We've got the following setup:

Epic assigned to user X for Sprint 1
Epic-subtasks created for same sprints but assigned to user Y for Sprint 1

Within User Y's planning board context for Sprint 1, we have the Epic sub-tasks mentioned above and a handful of other tasks.
The Epic Subtasks are all grouped together at the top of the list view. The following behaviour is observable:

• The Epic subtasks can be re-arranged amongst each other
• The tasks cannot be moved to a position between sub-tasks
• The Epic subtasks cannot be moved to a position between other tasks 

In our case, we don't want all of the sub-tasks to be completed as the top priority items. However, we cannot move the sub-tasks to a position lower on the planning board.
Correspondingly there's no way for us to move one of the tasks into a position higher than the sub-tasks.

Is this expected behaviour? 

Hi,

I created custom fileds "Rank" and "Story Point" and configured to render on Defect/Enhancement creation screens. "Story Point" is rendered on the screens but not the other one. Am i doing some thing wrong? Greenhopper is enabled so is that the reason?

 Thanks,

Srinivas

Hi, in planning board our sub-tasks don't stick with their parent. They randomly get attached to another task in planning mode (the data is correct when you open the single items though)

Any idea how we can repair this issue? Reïndexing didn't help.

We are using greenhopper 5.10.1 (on demand version)

 is there a way to group the linked issues together on the rapid board?  We see the issues and subtasks at the top of the screen, but the linked issues are at the bottom of the screen.  We want to be able to see all of the issues grouped together on the screen.

good Evening,

Our clients like to rank issues in a more user friendly manner using JIRA priority fields our developers prefer the granular green hopper ranking - in order to appeasecboth groups - is it possible to set up default mappings / cascading updates between these fields so that when our clients sets the priority, the ranking field automatically updates based on a rule set .

Please let me know if it's possible to achieve this kind of set up - even by alternative means

many thanks!

Barry merrill

Hi All,

I don't have the 'Rank' Context field available so I cant drag and drop to schedule tasks, can anyone help me with this?

thanks.

James

We have noticed that when using the ranking functionality, we can set the ranking but it is not maintained. We have set the ranking by drag and drop in the Planning board.  If you navigate away from the Planning board, the ranking is not maintained.  This also appears to happen across users.  The rank is set as one number for 1 user but another for another user. Is there something we need to change for the Rank to function properly?

Not being able to specify a Rank at Issue Creation time as of GH 5.8 is a real problem for us.

Our users will regularly break down a ranked Issue into several other issues, all of which we want to keep the same ranking for.  Now, when we break down an issue (by cloning it), the new Issue gets ranked to the bottom of the list forcing users to then go to the Agile side and manually drag and drop the new Issue to the spot below the initial ranked item.  This is a massive headache for us.  Is there a workaround to this?

Can the JIRA REST API be used to order stories for the Rapid Board?

I want to make a filter which gives me the issues from which the rank has been changed.

We are using the ranking functionality to give priority.

So I want to know the issues for which the priority has changed.

Something like this:

project = PROJECT and "Rank" changed BEFORE endOfWeek() AFTER startOfWeek()