Feature #5816
new issue initial status should be settable in workflow
| Status: | New | Start date: | 2010-07-05 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Issues workflow | |||
| Target version: | - | |||
| Resolution: |
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
History
#1 Updated by Norbert Bérci almost 2 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 almost 2 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 about 1 year 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 about 1 year ago
- Category changed from Issues to Issues workflow
#5 Updated by Terence Mill 4 months 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:(