Vote #63490: Fixing issues in commit messages can break the workflow - redmineorg-copy202205 - Redmine

編集操作

リンクをコピー

Vote #63490

未完了

Fixing issues in commit messages can break the workflow

Admin Redmine さんがほぼ2年前に追加. ほぼ2年前に更新.

ステータス:

Reopend

優先度:

高め

担当者:

カテゴリ:

Issues_2

対象バージョン:

開始日:

2008/06/21

期日:

進捗率:

予定工数:

Redmineorg_URL:

https://www.redmine.org/issues/1513

category_id:

version_id:

issue_org_id:

1513

author_id:

886

assigned_to_id:

comments:

status_id:

tracker_id:

plus1:

affected_version:

closed_on:

affected_version_id:

ステータス-->[Reopend]

引用

説明

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).

journals

Admin > Settings > Repositories > Fixing keywords > Applied status
--------------------------------------------------------------------------------
Great, thanks!
--------------------------------------------------------------------------------
I just checked this and I don't see any changes in this matter, so I'm reopening the bug.
--------------------------------------------------------------------------------
On recent versions you can already specify an "applied state", and the %Done to set, with associated keywords. If you want something else, could you please speak in terms of functionality and UI, and tell us how it could be integrated cleanly in the current version (0.9.6 today). Else I'll close this issue as I don't really see the point. Thank you
--------------------------------------------------------------------------------
I'm using 0.9.4, but I guess there shouldn't be any changes in 0.9.6 regarding this.

I think the problem is well described in the bug description (I know there is an "applied state" and that's not what I'm asking for, neither the problem I'm reporting). If I'm wrong please let me know which part is not clear enough and I'll try to explain it better.

This is not a feature request, it a defect (even when maybe a new feature, or an extension to an existing one would be needed to fix it), so please don't close it without a solution.

Thanks.
--------------------------------------------------------------------------------
I can confirm this issue also. It's still happening on the current trunk as of today. See also eg. duplicate #5906.
I'll change the "Affected version" accordingly.
--------------------------------------------------------------------------------
This is reported (in another way) again in #4648.
--------------------------------------------------------------------------------

related_issues

relates,New,4648,Using repository comments to change issue status conflicts with workflow
duplicates,Closed,5906,Changeset scanner doesn't check if status is within trackers workflow