Default Issue value problem in Workflow.
Added by Jorge S. almost 12 years ago
Hi, I have New and Confirmed, with Confirmed being able to be set after New.
However, in the creation time it is possible to check New or Confirmed, while what I want is to only allow New in the first instance.
In the Bug's Workflow I have:
Statuses ------------- New Statuses----------
New ----------------- New -- Confirmed (X) -- Others
Others
The problem seems to be that at creation time (before send), it has the New value evaluated, so it shows the Confirmed status...
I don't know if I am doing something wrong. Any help?
Thanks!
Replies (1)
RE: Default Issue value problem in Workflow.
-
Added by Gurvan Le Dromaguet almost 12 years ago
Hi,
I think you understood correctly the behavior.
What I did on my side is hiding the Status field on the "New Issue" form.
For this you can either use the hidden fields patch:
http://www.redmine.org/issues/12005
Or hack the app/views/issues code to hide it ...