Redmine

related to #8016

Thanks for quick update of the patch. I tried out the new patch and I think it is perfect.

Jean-Philippe Lang wrote:

Marius, thank you for submitting this patch but I prefer not to merge it into core. As you mentionned, we already have priorities that could be used to sort issues assigned to a version or start dates for those who would like a chronoligical sort. I prefer not to add another information on top of these existing things.

Thanks for you feedback even if is a very bad news for me/us.

We are using in our company Redmine for 3 years and no customer/project manager/scrum master used the prioritisation by priority, start dates or follows / precedes relations because the updates requires to many clicks and they are not so clear (if you have 4 tickets with priority Urgent, which one is more urgent?). Everyone wants a page where to move up / down the issues depending on the new priorities (which changes often in the Agile development).

Jean-Philippe Lang, is there anything I can make to have this feature implemented? I'm very sure that this feature is a must (almost all modern issue trackers has this implemented) and it'll be very useful for everyone (especially that you can enable/disable the feature). Maybe creating a new module called "Agile" which enables this feature is more appropriate than the new setting? Or more feedback from the community on this feature?

Thanks again.

One last remark:
These 2 types of prioritisation (by rank and by priority, start dates and relations) are not mutually exclusive. They work very well together because address different needs.

• The classical prioritisation can be used to make a release plan on med/long term which is useful to see it on a gantt chart.
• The prioritisation by rank (manually) can be used to plan the work for the next 2 weeks (on short term).

Marius BALTEANU wrote:

Jean-Philippe Lang, is there anything I can make to have this feature implemented? I'm very sure that this feature is a must (almost all modern issue trackers has this implemented) and it'll be very useful for everyone (especially that you can enable/disable the feature). Maybe creating a new module called "Agile" which enables this feature is more appropriate than the new setting? Or more feedback from the community on this feature?

More feedback from the community would certainly give to this patch more chance to be merged. It's not that I don't find the feature usefull, but few people have requested it for now. I left this tiket open so that people can express their feeling about this.

Jean-Philippe Lang wrote:

More feedback from the community would certainly give to this patch more chance to be merged. It's not that I don't find the feature usefull, but few people have requested it for now. I left this tiket open so that people can express their feeling about this.

Totally agree with this approach. Thank you again for your feedback, it really help me understands some of the decisions :)

I haven't applied the patch, but I have a question. Are the issues only re-orderable on the roadmap/version page or are they orderable on the issues page (with filters applied) too? I would definitely use this if implemented, but I would like to be able to re-order issues on the issues page so that I could focus on exactly what issues I wanted to order.

budo kaiman wrote:

I haven't applied the patch, but I have a question. Are the issues only re-orderable on the roadmap/version page or are they orderable on the issues page (with filters applied) too? I would definitely use this if implemented, but I would like to be able to re-order issues on the issues page so that I could focus on exactly what issues I wanted to order.

They are re-orderable only on the roadamp/version page because they are strictly related to a specific version (the position of the issue in that version/sprint). I'm going to investigate how can we extend the functionality also in the issues pages only if and when the patch is accepted.

+1
For agile development, I really want this feature.

Jean-Philippe Lang wrote:

More feedback from the community would certainly give to this patch more chance to be merged. It's not that I don't find the feature usefull, but few people have requested it for now. I left this tiket open so that people can express their feeling about this.

Registered just to vote for this. I've been looking through Redmine plugins over months looking for a good implementation for this, but found nothing quite satisfying.

In a world where people are "spoiled" by Trello and I assume the majority are doing some sort of agile/scrum with ordered backlogs, this is becoming very important in all planning tools.

Akipii Oga wrote:

+1
For agile development, I really want this feature.

Same for us. Such a feature would be great. We're currently experimenting with this agile plugin for Redmine. We'll see how it goes. ;-)

Jean-Philippe Lang wrote:

Marius BALTEANU wrote:

Jean-Philippe Lang, is there anything I can make to have this feature implemented? [...]

More feedback from the community would certainly give to this patch more chance to be merged. It's not that I don't find the feature usefull, but few people have requested it for now. I left this tiket open so that people can express their feeling about this.

Just FTR¹: based on Redmine.org tickets vote count list(2019/12/22) (which is based on '+1' count in issue journals), related issue #8016 is the 17th most "voted" for feature request.

¹ I don't plea for (immediate) integration of this patch, as I see some issues with the current approach.

I'm not familiar with Ruby, so could you help to install this patch, i.e. to explain how to install it? steps\little instruction.

thanks in advance!

+1
I want to cast my vote for drag-and-drop issue ordering.
We like small, focused issues, and as a result of that, we have a lot of them. Ordering them by setting the priority is cumbersome and does not give enough fine-grained control.
As a workaround for better ordering we are using the "Issues To-do Lists" plugin (http://www.redmine.org/plugins/redmine_issue_todo_lists), but I would really love this to be more integrated into Redmine core.

+1
Also have to use "Issues To-do Lists" plugin to set a sprint. Need to keep version and to do list equal by hands, which is very cumbersome.

Sortable target version issue list would be great!

Marius BALTEANU wrote:

Updated the patch to cleanly apply on the current trunk. Looking forward to see this patch committed.

Just applied your patch on our environment. Feels good - now we can finally organize a sprint without any workarounds.

• give ability to sort issue list by "position" column in custom queries
• IMHO "Enable manually set issue position in versions" should be per-version setting, with default value in global settings.

Marius BALTEANU did you ever look into prioritizing in the issues page? I like to prioritize my backlog and it would be nice to take advantage of the filters etc that are on that page.

I was also wondering where you updated the patch and when we can expect it to be merged into the main redmine build?

+1

This is great stuff. Thanks a lot.

We also need this mechanism.

Need this mechanism. https://www.redmine.org/boards/2/topics/54920

+1
We use priorities but we use only a few, we'd like to reorder things inside the same priority.
Thanks a lot guys!

+1
Is this latest patch compatible with the latest stable 4.1.1 ?
I think i have some mistakes

Ordering by priority/start date can be useful but as said, it's not as easy as drag/dropping issues to reorder them.
For me ordering is not always a matter of showing the chronology (or any other existing criteria) of the TODO list.
This drag & drop feature would be very useful for me but not only within versions (one does not prevent the other).

+1
This feauture is basic, indispensable and should really be implementend in core!

Found this issue while searching for a plugin which solves this fundamental need.

+1
Also note there appears to be a conflict between this current patch and the Agile plugin from RedmineUP.

That is if both are installed there is an error raised when one tries to create a subtask.

+1

+1. An absolute must have

Jean-Philippe Lang, just merge it, please!

I tried applying this patch on `4.2.7` and it did not work out of the box, had to manually copy over the diff and `git commit`.

Anyway, this patch is incompatible with the `redmine_agile` plugin since they delegate position on Issue:

`redmine_agile/patches/issue_patch.rb`:
```
delegate :position, :to => :agile_data, :allow_nil => true
```

A possible solution would be to rename the column to `fixed_version_position` but `acts_as_positioned` hardcodes the attribute to `position`, so a bigger change needs to be done in the core to allow `acts_as_positioned` with a different column. Another is to ask the folks at `redmineup` to not hijack the attribute on Issue.