| Reporter |
Фагим Садыков (Фагим.Садыков)
|
|---|---|
| Created | Oct 26, 2012 8:49:52 AM |
| Updated | May 14, 2013 5:56:01 PM |
What steps will reproduce the problem?
1.-10 Same as JT-17127
2.then - create another one version of project
3.move Subtask 2 to this version
4.refresh detailed view
What is the expected result?
I expect that AGILE, being setted on certain version will keep this context everywhere,
so i expected that Subtask2 will not be shown in version 1, but only in version 2
if it's parent task will be attached to veriosn 2 too.
It's not problem, that it can be situation, when some subtasks will be orphaned,
it will be simply detected with detail-tree view in usual (not-Agile ) issue view.
But much more worst is following situation:
a) I have Strategy Level project P1 with long-live tasks in swimlines, that are attached to many versions,
for example : "Improve performance of component group X", this project is visible only for project leads
b) I have Developer Level project P2 wich contains low-level tasks which must be assigned to certain version
and linked as subtasks to P1 tasks, this project is visible for all developers and some users
What happens instead?
So it's big trouble in AGILE when i open Version 10 for example and see 100+ tasks under "Improve performance of component group X" that was attached and fixed in versions from 1-9 or planed in "May Be at 2030 " version.
It's very big trouble, when U try to use agile for big, differently layered project with paralel versions and
inter-project relations.
Along with JT-17127 it is very expected that:
1. AGILE view match verison context (may be it can be switch-on-off parameter)
2. Shows ID link on 3-d level subtasks
3. So it does in tree view in common Issues view (now it shown non-matched subtasks/parenttasks as light-gray, but
in some cases I would prefere hide lowest level orpahns
1.-10 Same as JT-17127
2.then - create another one version of project
3.move Subtask 2 to this version
4.refresh detailed view
What is the expected result?
I expect that AGILE, being setted on certain version will keep this context everywhere,
so i expected that Subtask2 will not be shown in version 1, but only in version 2
if it's parent task will be attached to veriosn 2 too.
It's not problem, that it can be situation, when some subtasks will be orphaned,
it will be simply detected with detail-tree view in usual (not-Agile ) issue view.
But much more worst is following situation:
a) I have Strategy Level project P1 with long-live tasks in swimlines, that are attached to many versions,
for example : "Improve performance of component group X", this project is visible only for project leads
b) I have Developer Level project P2 wich contains low-level tasks which must be assigned to certain version
and linked as subtasks to P1 tasks, this project is visible for all developers and some users
What happens instead?
So it's big trouble in AGILE when i open Version 10 for example and see 100+ tasks under "Improve performance of component group X" that was attached and fixed in versions from 1-9 or planed in "May Be at 2030 " version.
It's very big trouble, when U try to use agile for big, differently layered project with paralel versions and
inter-project relations.
Along with JT-17127 it is very expected that:
1. AGILE view match verison context (may be it can be switch-on-off parameter)
2. Shows ID link on 3-d level subtasks
3. So it does in tree view in common Issues view (now it shown non-matched subtasks/parenttasks as light-gray, but
in some cases I would prefere hide lowest level orpahns