Project

General

Profile

Actions

Feature #4367

open

Ability to delete an issue status that is in use

Added by Holger Just about 14 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues planning
Target version:
-
Start date:
2009-12-09
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

I'm trying to restructure the workflow of some om my Redmine projects which involves changing the issue status definitions.

However, I am unable to delete a configures issue status if there are still issues with that status (as enforced from IssueStatus#check_integrity). While this is good and healthy, the failure message is not very talkative ("Unable to delete issue status").

It would be great if either

  1. the User would have the opportunity to select another status for the affected issues, or
  2. the error message would state the real problem
Actions #1

Updated by Holger Just about 14 years ago

However, the second option does not really solve the problem, as it is not possible to bulk edit all issues with that status, as there could also be issues in archived projects I do not know anything about. These still let check_integrity fail.

Actions #2

Updated by Jean-Philippe Lang about 14 years ago

  • Subject changed from Issue statuses can not be deleted if issues are still using it to Ability to delete an issue status that is in use
Actions #4

Updated by Michael Sanders over 9 years ago

+1

Actions #5

Updated by Toshi MARUYAMA over 9 years ago

  • Category changed from UI to Issues planning
Actions #6

Updated by Aron Rotteveel almost 9 years ago

+1

Actions #7

Updated by Greg T almost 7 years ago

+1 for more useful error messages at least.

I've had to find this SQL (after setting config.log_level = :info):
SELECT COUNT(*) FROM `trackers` WHERE `trackers`.`default_status_id` = 30

so that I could find out that not only issue statuses matter, but default statuses of trackers, too.

Actions #8

Updated by Guillermo ML almost 4 years ago

In #31361 (for 4.1.0) implemented the second option.
As you say in note-1 issues in archived projects could be a problem, these issue will not shown in a search. You'll have to search through a SQL query.

Actions #9

Updated by Greg T almost 4 years ago

Guillermo ML wrote:

In #31361 (for 4.1.0) implemented the second option.

I have 2 problems with that implementation:
  • the main one is lack of i18n;
  • the other is lack of details.
Actions

Also available in: Atom PDF