Feature #5332
closed
Allow bulk edit of issues from different projects
30%
Description
Say I have projects Foo and Bar, with Bar as a subproject of Foo.
Foo has some versions (1.0, 2.0, 3.0...) which are shared with Bar.
If I look at the Foo issue list, I also see Bar issues by default. But if I select some Foo issues and some Bar issues, then right-click, I cannot change the target version en masse—even though the projects have some target versions in common. In my case, both projects have exactly the same set of target versions.
This was a bit painful recently; I canceled a version and wanted to split its issues between two new versions.
Using git as of Apr 9, commit f3e375275964fe58b3962cffd33f89ba156e637e. (Ruby 1.8.7, Postgres 8.4.2, Rails 2.3.5.)
Related issues
Updated by Jean-Philippe Lang over 14 years ago
- Tracker changed from Defect to Feature
- Subject changed from Can't change target version of several issues in different projects to Allow bulk edit of issues from different projects
This is not supported for now.
Updated by Davide Ferrari over 14 years ago
Any plan to implement this some day? I'd like to see this feature too.
Updated by Burt Culver about 14 years ago
+1 - We would find this very helpful too
Updated by
Updated by Jean-Baptiste Barth about 14 years ago
- Status changed from New to 7
- Assignee set to Jean-Baptiste Barth
- Target version set to 1.1.0
As said on the forum, I'll take this one and we plan to support it for Redmine 1.1.0.
Updated by Jean-Baptiste Barth about 14 years ago
- % Done changed from 0 to 30
Versions are a specific case, but I committed changes to support bulk edit of others fields for issues from different projects, and also issue deletion. It will need some refactoring, but I encourage people interested in this feature to try it out from now and report any problem they may encounter.
FYI, here's the status of bulk edition on different projects:- shared versions: KO
- other fields (assignee, tracker, status, priority, etc.): OK
- delete issues: OK
- log time, watch, move, copy, duplicate: KO (was even KO on multiple issues from the same project)
Updated by Ewan Makepeace about 14 years ago
+1
We have a custom field 'Sprint' and every month I have to move all the active tasks to the next month. Because we have 8 sub projects I have to do this 9 times in total, even though they share the same field. It would be great if bulk edit on issues from different projects was allowed, perhaps by only offering the fields that were common to the selected issues?
Updated by Jean-Philippe Lang almost 14 years ago
- Target version changed from 1.1.0 to Unplanned backlogs
1.1 feature freeze.
Updated by Jean-Baptiste Barth almost 14 years ago
I think the actual version (things I committed in trunk) could be added to 1.1.0. It may need some refactoring1 but it works for main cases. Other cases need more work, except the watch/unwatch, and I don't know if we should handle them.
Jean-Philippe: let me know what you think.
1 I don't like all those @projects.map{}.inject{} but didn't know how we should handle it : extend Array in lib/redmine/core_ext/ OR introduce a new class to handle groups of projects, or groups of items ; if so, under Redmine:: scope or in a new model, etc.
Updated by Ryan Thrash almost 14 years ago
I'd really really like this. It'd help tremendously with sub-projects and Tasks release planning.
Updated by Anthony Meugui almost 13 years ago
+1 very helpful (in particular for shared version)
Updated by Jean-Philippe Lang over 12 years ago
- Target version deleted (
Unplanned backlogs) - Resolution set to Duplicate
1.4.0 lets you bulk edit issues from different projects.
Updated by Jean-Baptiste Barth over 12 years ago
- Assignee deleted (
Jean-Baptiste Barth)
Updated by Valdir Stiebe Junior over 12 years ago
This issue is marked as resolved, assigned and duplicate.
But it is assigned to nobody. And it is duplicate by #7087 which is also duplicate and closed.
At least on 1.4.2 we still can't select shared versions across projects when bulk editing multiple issues from different projects.
This is a "won't do" or it should be reopened?
Updated by Jean-Philippe Lang almost 12 years ago
- Status changed from 7 to New
Assigned issue with no assignee back to New status.
Updated by Olivier Houdas about 8 years ago
As far as I could see, this works fine in Redmine 3.x. This issue should be closed.
Updated by Toshi MARUYAMA about 8 years ago
- Status changed from New to Closed
Valdir Stiebe Junior wrote:
At least on 1.4.2 we still can't select shared versions across projects when bulk editing multiple issues from different projects.
I confirm it works on Redmine 3.3.1.