New feature request - prioritizing by drag drop

This is just a theoretical way of implementing that - not sure of practical challenges:
Users to associate a custom numeric field as the priority field in Planning board configuration. Greenhopper to then auto-manipulate this field when issues are drag-dropped on the planning board and move them.
That would be really cool!!!

Obviously, the sort field has to be that custom field for drag drop to work - drag drop disabled when any other sort field is chosen.

Hi Mayak,

Yeah that would be very cool indeed.
We do have a feature in our backlog that look a like.
It is a very challenging feature and we are up for it. It isn't prioritized yet and is more a nice to have for now but we will surely look at it in the future.

Cheers,

I want to second the desire for a way to sort issues in the way specified by Scrum and other Agile methodologies. (by value order 1,2,3,4,etc.)

Thanks for the great product!

I installed a demo of GreenHopper yesterday to take a look at it and showed it to two different development groups.
They both said the same thing - they would like to use it but only if it had this feature and it allowed them to do fine grained prioritisation.

For now you can use your own custom field to hold the priority (n priority) and use the sort by option in the context to display the Issues in the porper order.

What you cant do yet is the prioritize by drag and drop.

Cheers,

Unfortunately drag and drop is the bit the dev groups say they need - their current agile managment product gives them that.

I am not saying that we are not considering to support it in the future.

If the ability to prioritize by a drag and drop is more essential to your colleagues then all the other features that GreenHopper offers like:

1- Highlight
2- Filter
3- Card views with editable fields
4- Being Web base (remote)
5- Dynamic and filterable charts
6- Versions dependencies
7- Filterable Task board
8- Multi select
9- All what JIRA brings (Permission schemes, Workflows, Notifications ...)
10- The ability to use 1 tool for more then one purpose
and so on ...

then you are totally right. You are better of with your actual tool.
What I think is essential is that you select a tool that do fit your needs.

Cheers,

I have seen several teams trying to use various tools to help with managing an Agile process and they always get stuck when it comes to managing bugs.
Tools like scrumworks are good for story and backlog management but where do you put your bugs? Force them into scrumworks? Use a spreadsheet or use Jira in addition to another tool?

I have seen one team use scrumworks and Jira and excel to try and integrate the two. Scrumworks pro can integrate with jira but it's still clunky.

People who I have seen trying to use Jira for both backlog and bug management run into several into problems and one of the biggest is prioritisation. The Jira buckets for issues (critical blocker etc) just don't work for generating a proper work list e.g. There are 20 critical issues which one is the most/least important?

GreenHopper solves almost all of the problems with using Jira (and adds a huge amount to it) for backlog management but it doesn't fix prioritisation. It's a fundamental Jira problem not a criticism of GreenHopper.

Adding a custom field and sorting by it works but is still very clunky.
What we want is to be able to set a custom field as the prioritisation field and have GreenHopper manage it for us. Drag and Drop is just the way we would interact with the field. The important part is that we wouldn't have to go through and manually adjust the priority field on all issues when we change a particular issues priority.

Don't worry I didn't take it as a criticism and anyways I don't have the pretension to say that GreenHopper does answer all the needs.

I totally agree with you on the priority subject, and I also think it is fundamental. The custom field solution is just a workaround that, like most of workarounds, stays clunky.

Today we didn't find a robust solution that full fills this need.
We did try several paths but none was retained yet. It is not a trivial feature (we have to deal with a lot a parameters such as performance) and we don't want to make a mistake. The workaround is buying us some time but we are totally aware that it is just temporary.

I hope I am making some sens, if not please again don't hesitate.

Cheers,

We have scheduled some time this sprint to focus on a solution for this feature. We have a lot of questions.

Feel free to bring your inputs, we are pretty much open to any advise.

The task is:
http://www.greenpeppersoftware.com/jira/browse/GHS-132

Cheers,

The modeling of this feature went very well and the exploration was more then satisfying. This feature should be in the next release.

Yay! Thanks for your inputs and patience.

Cheers,

en4fzto-221vzgx-tw6q3091-0 <a href="http://www.url4.net/E46B87#2">slots</a>
http://www.url4.net/1AFDF9#1
online poker
http://www.url4.net/1AFDF9#4
[http://www.url4.net/1AFDF9#5 online casinos]
"phentermine":http://www.url4.net/2775C0#6
[LINK http://www.url4.net/4C89B4#7]soma[/LINK]

860g6uk-g85skqi-tw6q3ece-0 <a href="http://www.url4.net/1AFDF9#2">online casinos</a>
http://www.url4.net/E3E239#1
car insurance
http://www.url4.net/B3E8A8#4
[http://www.url4.net/4C89B4#5 soma]
"casinos":http://www.url4.net/21FD7F#6
[LINK http://www.url4.net/4C89B4#7]soma[/LINK]

gkl3n8u-0hvox05-tw6q5698-0 http://www.url4.net/E3E239#1
<a href="http://www.url4.net/982DCC#2">viagra</a>
online casinos
http://www.url4.net/21FD7F#4
[http://www.url4.net/CC5E6E#5 car insurance]
"poker":http://www.url4.net/E3E239#6
[LINK http://www.url4.net/F56DF2#7]zoloft[/LINK]

6yzt7f9-whdoqqd-tw6q5983-0 <a href="http://www.url4.net/7B7AA0#2">xanax</a>
http://www.url4.net/C534C3#1
viagra
http://www.url4.net/2775C0#4
[http://www.url4.net/7EAAED#5 health insurance]
"xanax":http://www.url4.net/7B7AA0#6
[LINK http://www.url4.net/C534C3#7]online poker[/LINK]