Project

General

Profile

Actions

Feature #13792

closed

Fixing via git push should not break workflow

Added by Ivan Kanis about 11 years ago. Updated over 8 years ago.

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

Is duplicate of Redmine - Defect #13762: SCM auto status change bypassses roles and permissionsConfirmed

Actions
Copied from Redmine - Feature #12814: Ability to specify target version sort orderReopened

Actions
Actions #1

Updated by Go MAEDA over 8 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Closing this issue as a duplicate of #13762.

Actions #2

Updated by Go MAEDA over 8 years ago

  • Is duplicate of Defect #13762: SCM auto status change bypassses roles and permissions added
Actions

Also available in: Atom PDF