プロジェクト

全般

プロフィール

Vote #68636

未完了

Allow subtasks to be affected to a different target version

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

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
-
開始日:
2010/11/17
期日:
進捗率:

0%

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

説明

We want to have subtasks assigned to be delivered in different Target Versions.
This doesn't seem to be possible - Redmine ignores any change of the Target Version for a subtask and sets it to be equal to that of the parent task.


journals

It will be even more difficult to calculate version progress, don't you think so ? Why don't you use issue relations instead of subtasks ?
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
The reason I would like this feature is that sometimes we have to pull a small part of a larger ticket out of a particular release, even if the main ticket remains in the release. Currently we have to remove the parent/child relation before we can move the subticket to another version.

--------------------------------------------------------------------------------
Calculating progress isn't as difficult as suggested: It's simply the average progress of all tasks assigned to a version that don't have a parent task assigned to the same version. The same holds for estimated times.

Having issues subtasks on different versions would help us a lot with the following use-case (for agile development):
- multiple product-projects (holding the backlogs)
- one sprint project - sprints are versions in the sprint project
- general user stories to track overall progress in the product-projects are assigned to product versions.
- more specific sub-user-stories that are assigned to sprints (target version)
--------------------------------------------------------------------------------
It is not only affecting subtasks, also story and all the related tasks. How did you organize the tasks of a story if you can not set different target version - by time instead of context - is there a workaround for agile development?
--------------------------------------------------------------------------------


related_issues

relates,Closed,5487,Allow subtasks to cross projects

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

  • カテゴリIssues_2 にセット

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

いいね!0
いいね!0