プロジェクト

全般

プロフィール

Vote #77913

未完了

Moving the parent issue from subproject to another project moves sub issues too

Admin Redmine さんが約2年前に追加. 約2年前に更新.

ステータス:
New
優先度:
高め
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
0
issue_org_id:
24111
author_id:
141723
assigned_to_id:
0
comments:
3
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
110
ステータス-->[New]

説明

If an issue with sub tasks is moved to another project (main project of the current one) the sub tasks are automatically moved to the new project, too.
Further no remark is written to the history of any of the tasks, neither to the parent nor to the sub task.

Environment:
  Redmine version                3.3.0.stable
  Ruby version                   2.1.9-p490 (2016-03-30) [i386-linux-gnu]
  Rails version                  4.2.6
  Environment                    production
  Database adapter               PostgreSQL
SCM:
  Subversion                     1.9.3
  Cvs                            1.12.13
  Git                            2.7.4
  Filesystem                     
Redmine plugins:
  redmine_agile                  1.4.0
  redmine_image_clipboard_paste  1.0.0
  redmine_mentions               0.0.1
  redmine_mylyn_connector        2.8.2.stable
  redmine_xapian                 1.6.4
  sidebar_hide                   0.0.7

journals

An important note to the sub tasks is, that the sub tasks has to be in the same project like the main task.
The project of sub tasks which belongs to another project are not changed.

Example:
<pre>
Project A
+- Sub project B
+- Sub project C

Main task (assigned to Sub project B)
+- sub task 1 (assigned to Sub project B)
+- sub task 2 (assigned to Sub project B)
+- sub task 3 (assigned to Sub project C)
</pre>

Moving _Main task_ from _Sub project B_ to _Project A_ moves _sub task 1_ and _2_ to _Project A_, too. _Sub task 3_ still remains in _Sub project C_. So the result looks like:
<pre>
Main task (assigned to Project A)
+- sub task 1 (assigned to Project A)
+- sub task 2 (assigned to Project A)
+- sub task 3 (assigned to Sub project C)
</pre>

But the expected result should look like:
<pre>
Main task (assigned to Project A)
+- sub task 1 (assigned to Sub project B)
+- sub task 2 (assigned to Sub project B)
+- sub task 3 (assigned to Sub project C)
</pre>
--------------------------------------------------------------------------------
Yes, it works like this by design but I understand that it may not be desirable to move subtasks too.
We can aither remove this behaviour (never move subtasks with parent task) or add a checkbox "Move subtasks too" when changing the project of a parent task.
--------------------------------------------------------------------------------
I think it would be better to add a checkbox when moving parent task because sometimes the whole task including subtasks should be moved to another project.
When the checkbox means "Move subtasks too", then it should be not checked per default. This is the main behaviour in our usage.
--------------------------------------------------------------------------------

Admin Redmine さんが約2年前に更新

  • カテゴリIssues_2 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0