Project

General

Profile

Actions
Copy link

Defect #10124

closed

Unable to select Status after changing an Issues Tracker

Added by Florian Mueller over 12 years ago. Updated about 1 month ago.

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

0%

Estimated time:
Resolution:
Fixed
Affected version:
1.3.0

Description

Hi,

Steps to reproduce:

I assume the trackers "bug" and "feature" exist. Now add a new status to feature which does not exist in the bug-workflow, e.g. "accepted" (and add that to feature's workflow).

Create a new feature, set the status to "accepted" and save it. Now update it and set the tracker to "bug" and save it again.

Now you are not able to change the status of that issue anymore, because there is no transition defined for status "accepted" to another one inside the bug's workflow.

Proposed Solution:

Fallback to the first status if the status set is not available in the current tracker's workflow.

Regards, Florian

Actions
Copy link
 #1

Updated by Go MAEDA about 1 month ago

  • Status changed from New to Closed
  • Resolution set to Fixed

Florian Mueller wrote:

Proposed Solution:

Fallback to the first status if the status set is not available in the current tracker's workflow.

At least Redmine 5.1 works that way. The default status for the tracker is selected in the "Edit" form if the original status is not allowed in the currently selected tracker.

Perhaps the behavior changed when #5991 was implemented in Redmine 3.0.0. Please see the comment at source:tags/3.0.0/app/models/issue.rb#L292.

  # Sets the tracker.
  # This will set the status to the default status of the new tracker if:
  # * the status was the default for the previous tracker
  # * or if the status was not part of the new tracker statuses
  # * or the status was nil
  def tracker=(tracker)
Actions
Copy link

Also available in: Atom PDF