Actions
Defect #23963
open
Bulk editing issues from various projects take us to Redmine's root (no project)
Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Affected version:
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).
Files
Related issues
Updated by Go MAEDA about 7 years ago
- Has duplicate Defect #27636: Redmine does not redirect to initial project page after bulk editing issues in different sub-projects. added
Actions