Feature #5816

New issue initial status should be settable in workflow

Added by Norbert Bérci over 7 years ago. Updated about 2 years ago.

Status:ClosedStart date:2010-07-05
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Issues workflow
Target version:3.2.0
Resolution:Fixed

Description

Is it possible to set the initial status(es) a new issue could be in at creation time? Currently it seems to allow the default status and all statuses reachable from the default status with one hop. This might be too permissive (for example I want to start in the "new" status only, and disallow its child statuses initially), or too restrictive (for example I might have two start statuses which are not in direct (1 hop) relation).

I propose a new (first) row named "initial status" (or something similar) on the workflow settings page where the admin can set which could be the initial status(es) of a newly created issue.


Related issues

Related to Redmine - Defect #5593: Meanless settings for workflow New 2010-05-25
Related to Redmine - Feature #5991: Tracker should have it's own default issue status Closed 2010-07-29
Related to Redmine - Feature #474: Status grouping New
Duplicated by Redmine - Feature #7311: Create new workflow for status Closed 2011-01-12
Duplicated by Redmine - Feature #558: Default & Closed statuses to be saved at workflow level Closed
Duplicated by Redmine - Feature #10864: Define initial issue status in workflow setting Closed
Duplicated by Redmine - Feature #19488: Add ability to configure selectable issue states when cre... Closed
Duplicated by Redmine - Feature #20718: No next issue status when creating new issue Closed
Duplicated by Redmine - Feature #2905: Enable per-tracker issue status set Closed 2009-03-05
Duplicated by Redmine - Feature #10601: Ability to force issues to be created with the default st... Closed
Duplicated by Redmine - Feature #3485: Closed statuses in dropdown for new issue (manager role) Closed 2009-06-12

Associated revisions

Revision 14458
Added by Jean-Philippe Lang over 2 years ago

Makes new issue initial status settable in workflow (#5816).

History

#1 Updated by Norbert Bérci over 7 years ago

If the proposed new row about initial statuses will be implemented, there is no use of the "Default value" column in Administration / Issue Statuses

#2 Updated by Nikolay Kotlyarov over 7 years ago

+1
I want more than only one default status.
Now it's not only one default: also this default will be used in every tracker, so as if this default status relates to every workflow:(

#3 Updated by Hans Bangkok over 6 years ago

A couple of different issues here.

As pointed out in the related report, it's quite possible as in my current use case that there is no one status that applies to all our trackers.

Therefore it should not be a requirement to have a single global "Default status", and that would be IMO easy to do away with. If the desire is simply to ensure there is a status on every issue, then an easy fix would be to check that when the issue gets saved.

Another way to go would be to present a dialog with a list of tracker types when "New Issue" is pressed, which would fit in OK with the idea of having a separate default for each tracker. However, the idea of forcing a subset of status's to be the only ones allowed at issue creation time seems overly complicated to me - I'm not saying there aren't use cases for it, just that it seems to me such a change would have further ramifications that need to be thought through.

#4 Updated by Etienne Massip over 6 years ago

  • Category changed from Issues to Issues workflow

#5 Updated by Terence Mill almost 6 years ago

Yeah, this is a big problem for us too.

We need different status sets in our trackers, so different start and finish status per tracker. At the moment there is one start status for all tracker's

This issue is duplicated by #558

Nikolay Kotlyarov wrote:

+1
I want more than only one default status.
Now it's not only one default: also this default will be used in every tracker, so as if this default status relates to every workflow:(

#6 Updated by Daniel Felix almost 5 years ago

I like this idea. It would help to improve redmines configurability!

#7 Updated by Roman Lukmanov almost 5 years ago

+1

#8 Updated by Etienne Massip almost 5 years ago

  • Target version set to Candidate for next major release

It should be done, I think the implementation proposed by Norbert in the first place is indeed the best one.

#9 Updated by VD DV over 4 years ago

+1

#10 Updated by Leonardo Salgado over 4 years ago

+1

#11 Updated by benoit deleris about 4 years ago

+1

#12 Updated by druidPollux - about 4 years ago

+1

#13 Updated by Anonymous about 4 years ago

I'm in the process of implementing Redmine as a new tracking system where I work (small team of 4 devs), this specific feature was one of the biggest concerns from management while I was giving a product demo...

So, here's a big +1 from me.

#14 Updated by Jimmy Engelbrecht about 4 years ago

+1

#15 Updated by Tamas Hock over 3 years ago

+1

#16 Updated by Enmos Proje over 3 years ago

+1

#17 Updated by Guillaume - about 3 years ago

+1 -> we're planning to move from trac to Redmine and this feature is also a concern for our team

#18 Updated by m mahdi almost 3 years ago

+1

#19 Updated by Johan Jäderblom over 2 years ago

I have made a fix for this. You can find a plugin here: https://github.com/Jaeder42/InitialStatusRedminePlugin

The plugin adds an initial status "Initital". It will be set as the first and as the default issue. You will need to assign statuses to it's workflow.

Once this is done, when you create a new issue, only the statuses which you have assigned in the workflow can be selected for the issue but one must be. As long as you do not link to the initial status it can't be set to this. The plugin also only alters the view for creating a new item.

Please try it and tell me if you have any trouble running it.

#20 Updated by Anonymous over 2 years ago

Johan Jäderblom wrote:

The plugin adds an initial status "Initital". It will be set as the first and as the default issue. You will need to assign statuses to it's workflow.

Interesting workaround.. Since Redmine allows new issues to use the selected "Default" status or any status that the default can move to in one step, hiding the "Default" status is quite literally the only way to get the UI to only show one status option for new issues.

Doesn't quite close the issue in question here, but I'll most definitely be using your plugin in the meantime.. :)

#21 Updated by Alex Petty over 2 years ago

For that matter, new issues should be settable only those tracker-types that are configured for the role.

I envision this workflow as follows:
(1) Administrator creates a role (let's call it role A)
(2) Administrator assigns a user (or group) role A.
(3) Through the implementation of this feature, the administrator will be able to define which tracker-types that role A is capable of creating (so long as role A has been assigned the "add issue" permission)
(4) When the user possessing role A (and also having the "add issue" permission) clicks the "New Issue" tab, the user will see only those trackers which were defined as "can create this tracker" to role A.
(5) If the user has multiple roles with "can create this tracker" defined, each having their own set of permissible trackers, the user will be able to create the super-set of all trackers from all assigned roles.

This feature would greatly enhance Redmine's flexibility in configuration.

#22 Updated by Jean-Philippe Lang over 2 years ago

  • Target version changed from Candidate for next major release to 3.2.0

#23 Updated by Go MAEDA over 2 years ago

  • Related to Feature #19488: Add ability to configure selectable issue states when creating new ticket added

#24 Updated by Go MAEDA over 2 years ago

  • Related to deleted (Feature #19488: Add ability to configure selectable issue states when creating new ticket)

#25 Updated by Go MAEDA over 2 years ago

  • Duplicated by Feature #19488: Add ability to configure selectable issue states when creating new ticket added

#26 Updated by Go MAEDA about 2 years ago

  • Duplicated by Feature #20718: No next issue status when creating new issue added

#27 Updated by Jean-Philippe Lang about 2 years ago

  • Subject changed from new issue initial status should be settable in workflow to New issue initial status should be settable in workflow
  • Status changed from New to Closed
  • Assignee set to Jean-Philippe Lang
  • Resolution set to Fixed

#28 Updated by Toshi MARUYAMA over 1 year ago

  • Duplicated by Feature #2905: Enable per-tracker issue status set added

#29 Updated by Go MAEDA about 1 year ago

  • Duplicated by Feature #10601: Ability to force issues to be created with the default status added

#30 Updated by Go MAEDA about 1 year ago

  • Duplicated by Feature #3485: Closed statuses in dropdown for new issue (manager role) added

Also available in: Atom PDF