Vote #77849
未完了Bulk editing issues from various projects take us to Redmine's root (no project)
ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:
0%
予定工数:
Redmineorg_URL:
category_id:
2
version_id:
0
issue_org_id:
23963
author_id:
80618
assigned_to_id:
0
comments:
1
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
110
説明
- Take a Redmine site having a tree of projects with at least 2 sub-projects in a master project.
- In the master project, list all issues from sub-projects
- 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).
journals
--------------------------------------------------------------------------------
related_issues
duplicates,Closed,27636,Redmine does not redirect to initial project page after bulk editing issues in different sub-projects.
いいね!0