| Reporter |
Фагим Садыков (Фагим.Садыков)
|
|---|---|
| Created | Mar 25, 2013 10:02:02 AM |
| Updated | Jun 17, 2013 8:56:56 PM |
| Priority | Normal |
| Type | Usability Problem |
| State | Open |
| Assignee | Vadim Gurov (vgurov) |
| Subsystem | Agile Board |
| Fix versions | 5.0 |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
What steps will reproduce the problem?
1. Create two versions (ex v1,v2)
2. Create swimline (ex task1) and assign it both v1,v2 as Fix Version
3. Assume that this task is as swimline in both sprint of Agile
4. Call "archive" command in administration tool on v1
What is the expected result?
1. v1 became readonly in agile
2. v2 still have not fixed long-live swimline task1
What happens instead?
1. v1 totally hided from agile
2. v2 doesn't show task1
Motivation - swimlines tend to be long-live and and cross-version, because they commonly mean regular project activity, for ex "documentation", "base API improvements" , "localization". And most of versions contain tasks in each.
So i expect that if task is not Fixed and have 2 or more versions on it it will be not archived with one version.
Visibility in Agile - it's very usefull to able to see old versions in Agile UI because it's more ergonimic that usual issues table.
And now "archive" means 3 concerns, not 1 - awaited "archive == mark OWN version's tasks as archived, make version readonly" - it's understandable semantic, but now "archive == mark all RELATED to version tasks as fixed, archived and hide them from Agile" - it's discouraged semantic of "version archivation".
I suggest to make third state along to realeased and archived - make "readonly" - it must prevent creation of new issues assigned to version, prevent setting this version for existed tasks, AGILE show this version without ability of drag-drop and other editing features.
1. Create two versions (ex v1,v2)
2. Create swimline (ex task1) and assign it both v1,v2 as Fix Version
3. Assume that this task is as swimline in both sprint of Agile
4. Call "archive" command in administration tool on v1
What is the expected result?
1. v1 became readonly in agile
2. v2 still have not fixed long-live swimline task1
What happens instead?
1. v1 totally hided from agile
2. v2 doesn't show task1
Motivation - swimlines tend to be long-live and and cross-version, because they commonly mean regular project activity, for ex "documentation", "base API improvements" , "localization". And most of versions contain tasks in each.
So i expect that if task is not Fixed and have 2 or more versions on it it will be not archived with one version.
Visibility in Agile - it's very usefull to able to see old versions in Agile UI because it's more ergonimic that usual issues table.
And now "archive" means 3 concerns, not 1 - awaited "archive == mark OWN version's tasks as archived, make version readonly" - it's understandable semantic, but now "archive == mark all RELATED to version tasks as fixed, archived and hide them from Agile" - it's discouraged semantic of "version archivation".
I suggest to make third state along to realeased and archived - make "readonly" - it must prevent creation of new issues assigned to version, prevent setting this version for existed tasks, AGILE show this version without ability of drag-drop and other editing features.