Defect #4648: Using repository comments to change issue status conflicts with workflow - Redmine

Actions

Copy link

Defect #4648

open

Using repository comments to change issue status conflicts with workflow

Added by Sebastian Cabot over 15 years ago. Updated about 13 years ago.

Status:

New

Priority:

Normal

Assignee:

Category:

SCM

Target version:

Start date:

2010-01-25

Due date:

% Done:

Estimated time:

Resolution:

Affected version:

Description

Consider the following status workflow options:
The Bug Tracker has both Resolved and Closed.
The Feature Tracker has only Closed.

If I configure the repository setting to use the fixes keyword to change the status to Resolved.
If I commit a change that says fixes #30 and #30 is a feature I will not be able to modify the status for that issue anymore (unless I change the workflow).

In my opinion it should be fixed to either allow different repository options per tracker (BEST)
Or to allow a status change hierarchy say first resolved than closed than x etc.
Or to allow specific status change from the comment (something like set #30 closed) - Maybe this should be implemented anyways
Or not to change the status to a status that is not in the workflow.

Related issues