That's clear; sorting of Issues works perfectly, but the business part of our team does not only like to rank issues they also like to rank the project's itself ("higher level").
Normally the project managers collect projects which are ranked / prioritizes by the management. Based on this ranking the user stories (issues) are created and solved.
I'm not entirely sure if a project is the correct thing to be used to cluster our stuff. For the project managers it would work fine cause they want to report on per project basis to the management. I've also thought about using epics which may would also do the job (?) but epics are not supported in greenhopper's kanban mode as far as I known.
We developed a plugin called Profields to create Project attributes (a kind of custom fileds but for projects). You can not only create a field with the ranking but any fields you want, with values extracted from external tables and many features project-oriented and very useful for the business departments.
You can see our landing (yesterday we delivered Profields 2.0) and see an overview of the features:
also we invite you to try it and see if Profields can meet your requirements. You can send your issues, questions and comments to our supporting system: http://www.madeira20.com (only sign up and go).
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
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