プロジェクト

全般

プロフィール

Vote #80925

未完了

Keep issue status when processing commit messages

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

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
Administration_8
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
8
version_id:
0
issue_org_id:
33626
author_id:
462585
assigned_to_id:
0
comments:
2
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
160
ステータス-->[New]

説明

Described well in [message#57210]

Confirmed using:
Ruby 2.3.8
MySQL 5.7
Redmine 4.1.1
Rails 5.2.4.2


journals

Changed description to use Redmine message link instead of external direct link.

FWIW: I don't get the problem of the OP of that forum thread. What he describes with:

> We are using the keyword "for" to mark commits that refer to a certain issue - but do not necessarily cause any change in its state.

is covered by the *referencing* keywords setting. The *fixing* keywords setting(s) expect a status (and/or done ratio) change, which seems implied by the functionality.

So, can you elaborate on this matter?

--------------------------------------------------------------------------------
Thank you Mischa for the quick reply

The issue to me is that when leaving the *Applies Status* blank the revisions fail to be linked to the issues.

I would expect either:
* when leaving the *Applied Status* blank that revisions get linked to the denoted issues but that the issue status remains unchanged
* the *Applied Status* to be mandatory (non-empty) when saving the *Repositories settings*

with the former being my personal preference.
--------------------------------------------------------------------------------

Admin Redmine さんがほぼ4年前に更新

  • カテゴリAdministration_8 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0