set Assigned status and Final Status differently per Issue Workflow
We have 2 different workflow's which both use some of the same issue status's. However in one workflow one status does not mean that the issue is final while in the second workflow it does. Since issue status's are not enabled (grayed out) on the Issue Workflow administration page, is it possible to set these differently somewhere else, per issue workflow and use the setting from the Issue Status administration page as a default?
rlevine
· 1 |
|
Thursday, November 11, 2010, 4:46:41 PM |
0
|
Not sure I follow your question. You are saying "in one workflow one status does not mean that the issue is final while in the second workflow it does", this is not possible the "final" property is in the status level, not the workflow. |
||||
|
0
|
That's right Mark. I have 2 issue tasks. One for new development which includes QA and release management as part of the work flow, and one task for QA of existing applications. In the dev task when an issue is marked as Testing Complete, the issue is not yet completed until it is marked as released, in the QA task when an item is marked as Testing Complete that is the final status for that issue type. Is this something you can allow in a future release? BTW, when is the next release going to be available and where can I find what will be included in it? |
||||
|
0
|
What you can do is create 2 statuses of "Testing Complete", mark one is final and use it in the workflow of the QA task and the other in the project workflow or other types. |
||||
|
0
|
That is my work around, however I think it would be beneficial to add this ability to a future release. |
||||
|
0
|
Feel free to add it to our list: http://gemini.countersoft.com |
||||
|
0
|
Created http://gemini.countersoft.com/issue/ViewIssue.aspx?id=4224&PROJID=2 Thanks |
||||
|