Project

General

Profile

Actions

Feature #1966

closed

Different set of Issue Statuses per Tracker

Added by Ingmar Heinrich over 15 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2008-09-29
Due date:
% Done:

0%

Estimated time:
Resolution:
Wont fix

Description

For various reasons, it would be great to have the possibility to use a different Issue Status set per Tracker. In my case, I would like to reflect a complex workflow with a Redmine Workflow, so I don't need Statuses like New or Accepted, but the things that have to be done.


Related issues

Related to Redmine - Feature #973: Assign different status sets and workflows for separate projectsNew2008-04-02

Actions
Actions #1

Updated by Dipan Mehta almost 11 years ago

Technically, issue statuses are NOT strictly restricted for specific trackers. However, every issue state transition is settable differently for each Tracker.

For example, a Bug goes to New -> Investigation -> In progress -> Fixed. But Feature can go through New -> Client Approval -> In progress -> Fixed. So it is possible set the workflow such that Investigation will never be part of Feature and Client Approval is never part of bug. This is quite possible through appropriate configuration.

Actions #2

Updated by Daniel Felix almost 11 years ago

  • Status changed from New to Closed
  • Resolution set to Wont fix

Well I would agree Dipan.

You can define different issue status to different trackers.
Just define them in the workflow section as needed. After that, everything should be fine.

In my eyes there is technically no code line to be changed. I'm closing this issue.

Actions

Also available in: Atom PDF