Project

General

Profile

Actions

Defect #1513

open

Fixing issues in commit messages can break the workflow

Added by Leandro Lucarella over 16 years ago. Updated almost 13 years ago.

Status:
Reopened
Priority:
High
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2008-06-21
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

I have a redmine instances with trackers with orthogonal states (for example, task have a state "done" instead of "fixed" for bugs). In the workflow, a task can never be in "fixed" state and for that reason, can't go to any other state from "fixed" state..

On the other hand, I have the option "Referencing and fixing issues in commit messages" activated but I can only specify one "Applied status" (which I have in fixed).

The problem is, if a commit message closes a task, the task is set to be in "fixed" state, but (apart from being wrong) it can't be changed (unless I make the workflow less restrictive, which I rather not).

So, I think it would be great if one can specify a "default" closed state for a tracker, and have a option in "Applied status" that says "Default closed state" or something like that, so when a commit closes an issue, the correct state can be set.

It would be great too if one can specify how to close the issue in the commit message (something like "closes #1234 (fixed)".

Thank you.

Using Redmine 0.7.2.1557 (MySQL).


Related issues

Related to Redmine - Defect #4648: Using repository comments to change issue status conflicts with workflowNew2010-01-25

Actions
Has duplicate Redmine - Defect #5906: Changeset scanner doesn't check if status is within trackers workflowClosed2010-07-19

Actions
Actions

Also available in: Atom PDF