https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292011-02-07T18:29:05ZRedmineRedmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249192011-02-07T18:29:05ZEtienne Massip
<ul></ul><p>That's not a defect, that is related to the way you configure your workflow in Administration / Workflow, isn't it ?</p>
<p>You can define assignable workflow states even after the Done status has been set.</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249222011-02-07T19:46:31ZMatthias Neubert
<ul></ul><p>This was my First idea. Indeed the done state priviously<br />Wasnt active for the trackr when redmine did set IT.Ny commit. But after<br />changing this the behavior remains the same.<br />So AT least in this rare case it is a Bug.</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249532011-02-08T08:43:04ZEtienne Massip
<ul></ul><p>Do you mean that the Done status has been set by commit although it wasn't allowed in the workflow, thus forbidding you to change it afterwards ?</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249572011-02-08T11:22:56ZMatthias Neubert
<ul></ul><p>Yes. Thats the situation. This is paired with an other problem either:<br />One cannot set different auto-commit states for different trackers.</p>
<p>E.g.: Tracker "feature" shall be set to state "Ready for test" when developer commite "fixes <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: One user's bad email address breaks all email notifications for everyone on a project (Closed)" href="https://www.redmine.org/issues/123">#123</a>"</p>
<p>but tracker "support" shall bis set to state "Done" e.g. because "Ready for test" doesn't make sense for this tracker (and there this tracker doesn't use the state "ready for test", but tracker "feature" does use it)</p>
<p>so <br />1. it shouldnt be allowed to redmine automatically set a ticket in a state which its tracker doesn't support.</p>
<p>2. it should be possible to assign different "fixes"- States for the differen trackers</p>
<p>I gues 2. point should be raised as a Feature ticket. I will do so if you want.</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249632011-02-08T13:57:04ZEtienne Massip
<ul></ul><p>1. Why don't you deactivate issue auto-update on commit (e.g. by removing the keyword list) or just change the applied state value if you don't want this state to be triggered ?</p>
<p>2. There is already <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Referencing and fixing issues in commit messages (New)" href="https://www.redmine.org/issues/1232">#1232</a>.</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249652011-02-08T14:52:06ZMatthias Neubert
<ul></ul><p>I changed the applied state to a state which every tracker with code changes has, but it remains to stay in the not anymore support state, which was set wenn the commit arrived.</p>
<p>for 2. I will look at this.</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249662011-02-08T15:05:45ZMatthias Neubert
<ul></ul><p>Regarding 2. :</p>
<p><a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Referencing and fixing issues in commit messages (New)" href="https://www.redmine.org/issues/1232">#1232</a> is not what I mean.</p>
<p>I don't mean: many different key words which either set different issue states whith their procentages.<br />(which would be finde also)</p>
<p>but I mean: <br />if <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: One user's bad email address breaks all email notifications for everyone on a project (Closed)" href="https://www.redmine.org/issues/123">#123</a> belongs to tracker "Feature" then "fixes <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: One user's bad email address breaks all email notifications for everyone on a project (Closed)" href="https://www.redmine.org/issues/123">#123</a>" means feature goes to "Ready for test"</p>
<p>if <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: One user's bad email address breaks all email notifications for everyone on a project (Closed)" href="https://www.redmine.org/issues/123">#123</a> belongs to tracker "Support" then "fixes <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: One user's bad email address breaks all email notifications for everyone on a project (Closed)" href="https://www.redmine.org/issues/123">#123</a>" means feature goes to "Done"</p>
<p>assuming that Support dosn't have the state "Ready for test" but has the state "Done"</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249722011-02-08T17:13:11ZMatthias Neubert
<ul></ul><p>Ok your suggestens fixed the problem:</p>
<p>first: I removed the fixes keyword<br />second: I select a automaticaly fixed state to a state all tracker have<br />third: I changed the workflow to be able to set from a (not anymore supported state) to "New" State, in order to reset the state<br />forth: From "New" state I now can set to "Done" or what ever is legal fpr the trackers workflow.</p>
<p>not the most intuitve way but at least it worked out.</p>
<p>should I raise a feature request issue in redmine tracker for the point 2. on my list?</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=249732011-02-08T18:17:43ZEtienne Massip
<ul></ul><p>Yes, please open a feature request, I will close the defect.</p>
<p>BTW, do you commit code for issues filed in a Support tracker ?</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=250092011-02-09T11:42:56ZMatthias Neubert
<ul></ul><p>No of course not, it was just an example which came to my mind.<br />But we have diffenrent trackers which don't have the same workflow but all may have code changes which<br />are commited.</p>
<p>what keywords the redmine project it self uses? I noticed that a commit is attached to a issue just by mentioning its number , eg. Bla bla (<a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: One user's bad email address breaks all email notifications for everyone on a project (Closed)" href="https://www.redmine.org/issues/123">#123</a>) <br />How is this achieved?</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=250152011-02-09T13:06:20ZEtienne Massip
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Invalid</i></li></ul><p>This is due to the special <code>IssueID</code> keyword, RedMine commits never update issue status or progress, they just add a ref.</p>
<p>Saw you filled in <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Different commit Keywords for each tracker (Closed)" href="https://www.redmine.org/issues/7590">#7590</a>, still keeping this one open as defect because maybe there should exist a control to prevent auto-update an issue with a status which does not exists in the tracker's workflow.</p> Redmine - Defect #7572: Commit driven state setting not changablehttps://www.redmine.org/issues/7572?journal_id=250172011-02-09T13:27:25ZEtienne Massip
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li><li><strong>Resolution</strong> deleted (<del><i>Invalid</i></del>)</li></ul>