We have JIRA 5.0 + GH 6.0
Projects which are NOT enabled for Greenhopper still show the 'Rank to bottom', 'Rank to top' and 'Agile Board' actions.
How can these be disabled ?
That's an improvement request in the making :-)
This JIRA instance is being used both for software development and for completely different purposes. The fact that the operation 'Rapid board' is there, requires us telling the users of the non-software development configuration to ignore it, which is not really 'enterprise-class'.
I don't agree with Shaun.I think there should be a fix for the issue GHS-5800.
1.) Only users with access to Greenhopper-activaed-projects can can open the Agile-context-menu. Why doesn't Jira disable the Agile-tab in a similar way as it is done with the Temop-tab, which people who aren't tempo-users can't see.
2.) What's the use for displaying the Agile-Link in the issue-detail-screen when there is no board connected with that issue. We have lots of users in our helpdesk-application who don't understand why this link isn't disabled.
thanks for your hint, but I think this doesn't meet my point. We work already with a permission scheme which gives to accasional users only the permissions they actually need. Our problem is, that there is no way to deactivate the Agile-Links for these occasional users although the project the occasional users have permission for isn't activated for Greenhopper.
Those buttons being there is not due to the desire for things to be "deeply integrated," it's just lack of thoroughness in the integration of GreenHopper and Jira. Of course if I don't include a project as a GreenHopper project I would not want any buttons related to it in my issue interface. To describe this as a desired feature seems disingenuous.
I got linked to this question via https://answers.atlassian.com/questions/98366/configure-number-of-action-buttons
I upvoted this answer. Why? This is not a "permissions" issue so much as a UI issue. Different users are focused on different aspects of JIRA's functionality. JIRA's UI needs to support that. As it is, the prominent top of the UI is for us WASTED ON BUTTONS OUR USERS WILL NEVER EVER EVER CLICK ON.
Thank you for listening. -danny
Since I'm in the situation where I inherited jira with GreenHopper installed, I've made the executive decision to simply turn off those buttons and see who complains. I doubt anyone will.
To turn off the functionality of Rank to Top and Rank to Bottom, go to Plugins > User-Installed Plugins > GreenHopper and disable "Ranking Issue Operation (greenhopper-rank-top-operation)" and "Ranking Issue Operation (greenhopper-rank-bottom-operation)"
Yes, agreed, it does. For me, I'm more worried about what uninstalling Greenhopper entirely would do to the legacy projects that are listed under it more than I am about preserving functionality that I'm pretty sure is currently unused. So, yes, I am disabling ranking for all projects by doing what I did.
neil1967's solution worked for me. In JIRA 7, to turn off the functionality of Rank to Top and Rank to Bottom, go to Plugins > Application Components > JIRA Agile and disable "Ranking Issue Operation (greenhopper-rank-top-operation)" and "Ranking Issue Operation (greenhopper-rank-bottom-operation)"
I have to agree with Shaun. Anyway if you want to prevent people from ranking issues (in general), there is a permission for that. Look for "Schedule Issues" in your permission scheme. You also could create different permission scheems for projects using GreenHopper and for those projects not using Greenhopper and than granting this permission to people or not in each scheme.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs