プロジェクト

全般

プロフィール

Vote #73165

未完了

using commit keyword to update issue's status sets issue to a status that is not defined in the tracker.

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

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

0%

予定工数:
category_id:
3
version_id:
0
issue_org_id:
12879
author_id:
68263
assigned_to_id:
0
comments:
1
status_id:
1
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

I added a feature request in #12656 because the commit keyword that sets a special status should be configurable for each tracker.
For my workflows "feature requests" and "errors" have the status "ready for review / testing" before they can be closed. Closing tickets is done manually by the persons that do our software tests.

There is also a tracker "Simple Task" that does not have the status "ready for review / testing" included.

Our developers love the possibility to change the issue's state with a simple commit because they do not need to change a ticket manually and they also want to use this feature for their "simple tasks". The problem is that whenever they use the commit keyword for "Simple Tasks" the referenced issue is set to a status "ready for review" but this state is not defined in the tacker's (Simple Task) workflow.

Maybe this could be solved with #12656 or otherwise - if the status is not used in the workflow, the next status could be automatically set? (In my case: "Closed"). Another solution would be not to change the issues status if the status configured for the commit keyword does not exist - but this would not be the solution I would prefer ;-)

Thanks for your work!


journals

--------------------------------------------------------------------------------


related_issues

relates,Closed,12656,make commit keywords and issue ratio configurable for each tracker

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

  • カテゴリSCM_3 にセット

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

いいね!0
いいね!0