Defect #23963

Bulk editing issues from various projects take us to Redmine's root (no project)

Added by Olivier Houdas over 5 years ago.

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

0%

Category:Issues
Target version:-
Resolution: Affected version:3.3.0

Description

1. Take a Redmine site having a tree of projects with at least 2 sub-projects in a master project.
2. In the master project, list all issues from sub-projects
3. Select 2 issues from each sub-project, right-click and choose Modify
Result: On the Modification landing page, there is no project set. We have lost our project's tabs
Expected result: Either stay in the source project, or assign the first common parent project of all chosen issues to be the current project

I can suggest the attached code for implementing the second solution (based on redmine 3.3.0).

bundle-update-set-project.patch Magnifier (1.89 KB) Olivier Houdas, 2016-09-30 15:14


Related issues

Duplicated by Redmine - Defect #27636: Redmine does not redirect to initial project page after b... Closed

History

#1 Updated by Go MAEDA over 4 years ago

  • Duplicated by Defect #27636: Redmine does not redirect to initial project page after bulk editing issues in different sub-projects. added

Also available in: Atom PDF