Actions
Feature #13792
closedFixing via git push should not break workflow
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Duplicate
Description
We are running Redmine to 2.2.0.
Our typical workflow is New -> Assigned -> Fixed -> Verified -> Close
When we do push with git we run a hook to update bugs:
curl -sk "https://redmine.vo.com/sys/fetch_changesets?id=${id}&key=${key}"
Bugs that are referenced in the commit message are indeed Fixed.
However, we don't want this mechanism to break our workflow. I mean that an issue that is New or Verified should not become Fixed.
Am I making sense ?
Related issues
Updated by Go MAEDA almost 9 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Closing this issue as a duplicate of #13762.
Updated by Go MAEDA almost 9 years ago
- Is duplicate of Defect #13762: SCM auto status change bypassses roles and permissions added
Actions