Feature #22802

Add the posibility to set/change the position of an issue in a version

Added by Marius BALTEANU 11 months ago. Updated 12 days ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues planning
Target version:-
Resolution:

Description

In the roadmap tab, issues are now automatically sorted (positioned) in a version after tracker type (alphabetically) and created date (older first).

It'll be great to have the possibility to manually set and change the position of an issue in a version. In this way, the users will have more ways to prioritize the work in a version.

Our use case: We use the versions as sprints (time based) and for each version we plan some issues that the team should implement in the next period. Having this feature available, we'll be able the set also the order in which the features should be implemented (issues positioned in the top of the version are the most important).

This mechanism is very used in the modern software development (like scrum, kanban) and is an alternative to the classical planning (with start date, due date and follows/precedes relations) which are great also, but not so easy to use in teams that periodically release issues and the priorities change often.

A similar implementation like in the #12909 is enough in my opinion and the drag'n'drop mechanism should be available only in the roadmap tab and version page. In the future, this feature can be extend also to allow drag'n'drop issues from one version to another.

issues_sortable.png (64.4 KB) Marius BALTEANU, 2016-09-06 01:47

manual_set_issue_position_in_versions.patch Magnifier (19.6 KB) Marius BALTEANU, 2016-09-06 01:55

manual_set_issue_position_in_versions_v2.patch Magnifier (22.4 KB) Marius BALTEANU, 2016-09-06 08:41

manual_set_issue_position_in_versions_v3.patch Magnifier (15 KB) Marius BALTEANU, 2016-11-19 08:34


Related issues

Related to Redmine - Feature #8016: Drag-and-drop issue (ticket) ordering New 2011-03-30

History

#1 Updated by Marius BALTEANU 7 months ago

related to #8016

#2 Updated by Marius BALTEANU 7 months ago

I made a patch that implements this feature using the drag and drop implementation from #12909.

The patch adds the following changes:
  • a new setting in Issue tracking to enable/disable this feature (called "Enable manually set issue position in versions").
    When it is disabled (default setting), the issues are sorted in versions as it is in current trunk version.
    When it is enabled, the users can manually change issue position in the respective version. Print-screen below.
  • the drag and drop mechanism in roadmap (index) and version (show) page.
  • adds new tests and passes the existing ones
  • position changing is not journalized because this info is not so relevant in issue history.

In my opinion, this feature is a must for an issue tracking system and beside that, it'll be very useful for other plugins (like Agile, Backlogs or Scrum) to build their own view with cards on a core functionality. Even if we use the Agile plugin in our company, most of the users try to prioritise the issues from Roadmap tab and complains why doesn't work.

Any feedback on this feature is really appreciated.

#3 Updated by Go MAEDA 7 months ago

  • Target version set to Candidate for next major release

Marius BALTEANU, thank you for sharing the great patch! It is very useful for agile development.

But I think we need a permission to restrict reordering to particular roles. In current implementation, even anonymous user can reorder issues.

#4 Updated by Go MAEDA 7 months ago

  • Related to Feature #8016: Drag-and-drop issue (ticket) ordering added

#5 Updated by Marius BALTEANU 7 months ago

Go MAEDA wrote:

But I think we need a permission to restrict reordering to particular roles. In current implementation, even anonymous user can reorder issues.

Thanks for your feedback, I've updated the patch to include a new permission which allows users to change the issue position in a version. I didn't use the existing manage versions permission because I think that are 2 different activities.

Please let me know if more work is required to have this implemented.

#6 Updated by Go MAEDA 7 months ago

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

#7 Updated by Toshi MARUYAMA 7 months ago

  • Target version changed from Candidate for next major release to 3.4.0

#8 Updated by Marius BALTEANU 4 months ago

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

#9 Updated by Jean-Philippe Lang 4 months ago

  • Target version deleted (3.4.0)

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.

#10 Updated by Marius BALTEANU 4 months ago

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.

#11 Updated by Marius BALTEANU 4 months ago

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.

For example:
  • 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).

#12 Updated by Jean-Philippe Lang 4 months ago

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.

#13 Updated by Marius BALTEANU 4 months ago

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 :)

#14 Updated by budo kaiman 4 months ago

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.

#15 Updated by Marius BALTEANU 4 months ago

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.

#16 Updated by Akipii Oga 3 months ago

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

#17 Updated by Thomas Ferris Nicolaisen about 1 month ago

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.

#18 Updated by Marcel Liebischer about 1 month ago

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. ;-)

#19 Updated by Mischa The Evil about 1 month ago

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 FTR1: based on Redmine.org tickets vote count list (which is based on '+1' count in issue journals), related issue #8016 is the 17th most "voted" for feature request.

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

#20 Updated by Sergey Nazarenko about 1 month ago

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!

#21 Updated by Bodo Maass 12 days ago

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.

Also available in: Atom PDF