Actions
Defect #5906
closedChangeset scanner doesn't check if status is within trackers workflow
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-07-19
Due date:
% Done:
0%
Estimated time:
Resolution:
Duplicate
Affected version:
Description
The current changeset scanner/parser doesn't check if the status it is about to be set to is within the trackers workflow.
For example, I have a 'Feature' tracker with issue #1337 and a 'fixing keyword' setup of 'Fixed'. If within a commit message I enter in 'Fixed #1337' the status of this issue will be set to 'Fixed'. However, 'Fixed' isn't within the 'Feature' tracker workflow since we don't fix features, we implement them.
This has lead to issues when it comes to altering the status of this issue, since I can't change it to anything as 'Fixed' is not within the workflow.
Related issues
Updated by Mischa The Evil over 14 years ago
- Status changed from New to Closed
- Affected version (unused) set to devel
- Resolution set to Duplicate
Closed as a duplicate of issue #1513.
Alex: thanks for bringing this up again...
Actions