https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292012-04-05T10:11:42ZRedmineRedmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372272012-04-05T10:11:42Zfangzheng (方正)
<ul></ul><p>I think this feature will certainly be added, sooner or later.<br />Most bug trackers have this feature now.</p> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372732012-04-06T13:31:16ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Tracker</strong> changed from <i>Defect</i> to <i>Feature</i></li><li><strong>Subject</strong> changed from <i>New issue page lists default status with others statuses configured in workflow despite of understanding that issue isn't a created yet to change status from default one to another one.</i> to <i>Ability to force issues to be created with the default status</i></li></ul><p>This is how it was working in the very early versions of Redmine but the current behaviour was requested a long time ago in <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Set status when raising issue (Closed)" href="https://www.redmine.org/issues/312">#312</a>.</p> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372752012-04-06T14:30:15ZY Z
<ul></ul><p>I took at look at that issue and understood their reason to do this. Honestly I don't think that currently working solution make any sense at least because it's confused to see the long list of the statuses if they are open / available to be selected from "New".</p>
<p>I believe community set their vote as well here and ideally it would be nice to have an option (checkbox in Settings for example) to choose between displaying and hiding all the target statuses.</p>
<p>Does it make sense?</p> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372762012-04-06T14:38:39ZEtienne Massip
<ul></ul><p>I disagree and want to be able to create an issue directly in a specific status when it is required rather then create it and update the status right after.</p> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372772012-04-06T15:05:30ZY Z
<ul></ul><p>It depends on the requirements how redmine should be configured for specific purposes. Redmine is flexible application and people have been using it to track lots in different contexts.</p>
<p>I believe the current behavior is ambiguous at least because New issue has no any status, however it has already included all the available for "New" roads.</p>
<p>Secondly, I have been tracking time for every status precisely and handle each status differently by having important notifications. <br />If somebody creates issue with different status except for New, some of the notifications are getting lost and our tracking schema becomes inconsistent.</p>
<p>I don't want to say that current version is working improperly, however it has this disadvantage in real business usage.</p> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372782012-04-06T15:12:37ZEtienne Massip
<ul></ul><p>Yura Zaplavnov wrote:</p>
<blockquote>
<p>It depends on the requirements how redmine should be configured for specific purposes. Redmine is flexible application and people have been using it to track lots in different contexts.</p>
</blockquote>
<p>A good application is not too much flexible. Specific neds should be implemented with plugins.</p>
<blockquote>
<p>I believe the current behavior is ambiguous at least because New issue has no any status, however it has already included all the available for "New" roads.</p>
<p>If somebody creates issue with different status except for New, some of the notifications are getting lost and our tracking schema becomes inconsistent.</p>
</blockquote>
<p>If this person has a role that allow her/him to set a status different from New at creation, then you should assume that she/he knows what she/he's doing.</p>
<p>If not then her/his role and the workflow should no allow her/him to set a different status.</p>
<p>IMO.</p> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372802012-04-06T16:25:20ZY Z
<ul></ul><p>Again, it generally depends on the flow for the business process. For example I have to track every status where each person within a project is able to set it starting from <strong>Default</strong> one (New status in my case).</p>
<p>Maybe it's possible to configure the roles somehow to let person start issue from New status only and change the status to another one as soon as issue is created?</p> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372822012-04-06T17:39:23ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><blockquote>
<p>Maybe it's possible to configure the roles somehow to let person start issue from New status only and change the status to another one as soon as issue is created?</p>
</blockquote>
<p>This is too complicated IMO but a simple option for enabling/disabling this behaviour globally would be fine.</p>
<p>It should be trivial to change this behaviour (untested):</p>
<pre>
Index: app/models/issue.rb
===================================================================
--- app/models/issue.rb (revision 9330)
+++ app/models/issue.rb (working copy)
@@ -511,6 +511,7 @@
# Returns an array of status that user is able to apply
def new_statuses_allowed_to(user=User.current, include_default=false)
+ return [IssueStatus.default] if new_record?
statuses = status.find_new_statuses_allowed_to(
user.admin ? Role.all : user.roles_for_project(project),
tracker,
</pre> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=372842012-04-06T17:55:31ZY Z
<ul></ul><p>Ok, will try to change and test it. I think it would be useful to extend redmine functionality to have this option in future versions.</p>
<p>Thanks for the help!</p> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=732252016-09-04T01:37:11ZGo MAEDA
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/5816">Feature #5816</a>: New issue initial status should be settable in workflow</i> added</li></ul> Redmine - Feature #10601: Ability to force issues to be created with the default statushttps://www.redmine.org/issues/10601?journal_id=732272016-09-04T01:38:30ZGo MAEDA
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul><p>Implemented by <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: New issue initial status should be settable in workflow (Closed)" href="https://www.redmine.org/issues/5816">#5816</a> (Redmine 3.2.0).</p>