htietgens - these operations should only be available to users who have the Schedule Issues permission for the given issue.

Thanks,

I need a way to suppress these buttons for users which should not be able to rank issues. Is there a way to do this?

Shaun,

The more I have used this, the better I have liked this feature. Very easy to use. It is intuitive and works very well. Can't wait for the scrum to also come out.

Shaun,

I spent some more time and I see how things are working now.

Thanks
Ali

Shaun,

Would you help me understand, how a project for which GH is not enabled can use this new "feature". I spent some time with our JIRA instance but can not see how these three new options are benefiting me in a project for which GH is not enabled. Searching the web resulted in nothing.

Thanks
Ali

From: Shaun Clowes [Atlassian] (JIRA) [jira@atlassian.com]
Sent: Sunday, April 29, 2012 12:27 AM
To: Ali Behboodian
Subject: [JIRA] (GHS-4676) Rank to Top and Rank to Bottom options showing for non GreenHopper Projects on view issue page

[ https://jira.atlassian.com/browse/GHS-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308783#comment-308783 ]

Shaun Clowes [Atlassian] commented on GHS-4676:
-----------------------------------------------

Hi Ali,

The 'enabled for GreenHopper' setting only applies to the Planning/Chart/Release Boards, all projects in the system can be used with the new Rapid Board. We currently have no plans to change this.

Thanks,
Shaun

–
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.atlassian.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Hi Ali,

The 'enabled for GreenHopper' setting only applies to the Planning/Chart/Release Boards, all projects in the system can be used with the new Rapid Board. We currently have no plans to change this.

Thanks,
Shaun

Thanks Shaun for your reply.

We have one project in JIRA that our HR team uses for HR purposes and one that our software team uses. "Cross project ranking" in this case brings no benefit.

Regardless, can you help me understand, when GH is disabled for my project, how am I going to benefit from the rankings. I thought ranking is only visible when you have GH enabled for a project. Otherwise, we would not see the rankings.

Thanks
Ali

Hi Ali,

Many users have asked to be able to rank from the view issue page because they end up there from JIRA notification emails and when running JQL reports.

GreenHopper uses a global ranking system. All issues are ranked against all others. This is actually a very useful arrangement since it allows cross project ranking. Even more useful is the fact that users don't ever really look at the rank of all issues, just subsets (for example two projects), which means that Rank To Top/Bottom will always send the issue to the top or bottom of Rapid Boards which include that issue and have no effect on other boards/users. The end result is that from a user's point of view Rank to Top/Bottom always send the issue to the top or bottom of their Rapid Boards just as they expect it to.

Thanks,
Shaun

Unfortuanelty, this adds clutter and will make the use and adoption of JIRA more difficult. If the user deos not need to use the rank why are we giving them the option. Also, why should we care about ranking all the issues in the system. Most the projects we have are unrelated and worked on by different teams. This seems to be a bug that is turned to a feature

This is expected behaviour. GreenHopper now uses a Global Rank which means that all issues in the system have a rank. The user does not need to use the rank or view those projects in GreenHopper however.

Thanks,
Shaun