Project

General

Profile

Actions

Defect #16366

closed

Issue ends up in an invalid state of a specified tracker

Added by Jan-Willem Stroeken almost 10 years ago. Updated over 8 years ago.

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

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

When using two trackers (default 'bug' and extended 'bug2', 'bug2' has been extended with an additional state 'waitForConfirmation' ) assume the following scenario:
- create 'issue1' in tracker 'bug2'
- set state of 'bug2' to 'waitForConfirmation'
- set 'issue1' tracker to 'bug' and save it
- 'issue1'is now using the 'bug' tracker and in the 'waitForConfirmation' state. The state cannot be changed anymore

in order to restore this, revert 'issue1'to 'bug2', set state to a supported state and then change trackertype

The tracker/state combination seems only to be checked when setting them together in one edit. When editing them sequentially (workflow first, state secondly), there is no check on the validity of the resulting state

Environment:
Redmine version 2.3.4.stable
Ruby version 1.9.3-p0 (2011-10-30) [x86_64-linux]
Rails version 3.2.13
Environment production
Database adapter Mysql2

Actions

Also available in: Atom PDF