Project

General

Profile

Actions

Feature #5816

closed

New issue initial status should be settable in workflow

Added by Norbert Bérci over 13 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Category:
Issues workflow
Target version:
Start date:
2010-07-05
Due date:
% Done:

0%

Estimated time:
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: Grey out workflow checkboxes for transitions to the same statusClosedJean-Philippe Lang2010-05-25

Actions
Related to Redmine - Feature #5991: Tracker should have it's own default issue statusClosedJean-Philippe Lang2010-07-29

Actions
Related to Redmine - Feature #474: Status groupingNew

Actions
Has duplicate Redmine - Feature #7311: Create new workflow for statusClosed2011-01-12

Actions
Has duplicate Redmine - Feature #558: Default & Closed statuses to be saved at workflow levelClosed

Actions
Has duplicate Redmine - Feature #10864: Define initial issue status in workflow settingClosed

Actions
Has duplicate Redmine - Feature #19488: Add ability to configure selectable issue states when creating new ticketClosed

Actions
Has duplicate Redmine - Feature #20718: No next issue status when creating new issueClosed

Actions
Has duplicate Redmine - Feature #2905: Enable per-tracker issue status setClosed2009-03-05

Actions
Has duplicate Redmine - Feature #10601: Ability to force issues to be created with the default statusClosed

Actions
Has duplicate Redmine - Feature #3485: Closed statuses in dropdown for new issue (manager role)Closed2009-06-12

Actions
Has duplicate Redmine - Feature #18037: default status per workflowClosed

Actions
Has duplicate Redmine - Defect #14274: Default Issue Value Workflow doesn't work as expectedClosed

Actions
Actions #1

Updated by Norbert Bérci over 13 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

Actions #2

Updated by Nikolay Kotlyarov over 13 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:(

Actions #3

Updated by Hans Bangkok almost 13 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.

Actions #4

Updated by Etienne Massip almost 13 years ago

  • Category changed from Issues to Issues workflow
Actions #5

Updated by Terence Mill about 12 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:(

Actions #6

Updated by Daniel Felix about 11 years ago

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

Actions #7

Updated by Roman Lukmanov about 11 years ago

+1

Actions #8

Updated by Etienne Massip about 11 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.

Actions #9

Updated by VD DV almost 11 years ago

+1

Actions #10

Updated by Leonardo Salgado almost 11 years ago

+1

Actions #11

Updated by benoit deleris over 10 years ago

+1

Actions #12

Updated by druidPollux - over 10 years ago

+1

Actions #13

Updated by Anonymous over 10 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.

Actions #14

Updated by Jimmy Engelbrecht over 10 years ago

+1

Actions #15

Updated by Tamas Hock almost 10 years ago

+1

Actions #16

Updated by Enmos Proje almost 10 years ago

+1

Actions #17

Updated by Guillaume - over 9 years ago

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

Actions #18

Updated by m mahdi about 9 years ago

+1

Actions #19

Updated by Johan Jäderblom almost 9 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.

Actions #20

Updated by Anonymous almost 9 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.. :)

Actions #21

Updated by Alex Petty over 8 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.

Actions #22

Updated by Jean-Philippe Lang over 8 years ago

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

Updated by Go MAEDA over 8 years ago

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

Updated by Go MAEDA over 8 years ago

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

Updated by Go MAEDA over 8 years ago

  • Has duplicate Feature #19488: Add ability to configure selectable issue states when creating new ticket added
Actions #26

Updated by Go MAEDA over 8 years ago

  • Has duplicate Feature #20718: No next issue status when creating new issue added
Actions #27

Updated by Jean-Philippe Lang over 8 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
Actions #28

Updated by Toshi MARUYAMA over 7 years ago

  • Has duplicate Feature #2905: Enable per-tracker issue status set added
Actions #29

Updated by Go MAEDA over 7 years ago

  • Has duplicate Feature #10601: Ability to force issues to be created with the default status added
Actions #30

Updated by Go MAEDA over 7 years ago

  • Has duplicate Feature #3485: Closed statuses in dropdown for new issue (manager role) added
Actions #31

Updated by Go MAEDA about 6 years ago

Actions #32

Updated by Go MAEDA over 2 years ago

  • Has duplicate Defect #14274: Default Issue Value Workflow doesn't work as expected added
Actions

Also available in: Atom PDF