Vote #77439
未完了Add the posibility to set/change the position of an issue in a version
0%
説明
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.
journals
related to #8016
--------------------------------------------------------------------------------
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.
!issues_sortable.png!
* 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.
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
Thanks for quick update of the patch. I tried out the new patch and I think it is perfect.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Updated the patch to cleanly apply on the current trunk. Looking forward to see this patch committed.
--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------
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":https://zitec.com 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.
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).
--------------------------------------------------------------------------------
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":http://www.redmine.org/plugins/redmine_agile 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[1]: based on message#51899 (which is based on '+1' count in issue journals), related issue #8016 is the 17th most "voted" for feature request.
fn1. 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.
As an idea for enhancement:
* 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
--------------------------------------------------------------------------------
Hello,
Here the patch fixed for the last stable version : v4.1.1
Don't forget to add the permission to your group et run the migration :
<pre>
cd /var/www/redmine
rake db:migrate RAILS_ENV=production
</pre>
Max
--------------------------------------------------------------------------------
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).
--------------------------------------------------------------------------------
Hello,
Just add the possibility to sort issues by position from the REST API.
Example:
<pre>
https://xxx/issues.json?fixed_version_id=35&sort=position,id
</pre>
Max
--------------------------------------------------------------------------------
Fix default order
--------------------------------------------------------------------------------
+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!
--------------------------------------------------------------------------------
related_issues
relates,New,8016,Drag-and-drop issue (ticket) ordering
relates,New,23287,Better structuring of Version page