Defect #33626

Keep issue status when processing commit messages

Added by Wouter Peers over 2 years ago. Updated over 2 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution: Affected version:4.1.1


Described well in [Keep issue status when processing commit messages]

Confirmed using:
Ruby 2.3.8
MySQL 5.7
Redmine 4.1.1


#1 Updated by Mischa The Evil over 2 years ago

  • Description updated (diff)

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?

#2 Updated by Wouter Peers over 2 years ago

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.

Also available in: Atom PDF