Defect #5587

Custom fields 'required' not taking Tracker into account

Added by Oskar Nordquist over 12 years ago. Updated about 2 years ago.

Status:NewStart date:2010-05-25
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution: Affected version:


Try adding a required custom field only valid for one tracker. Now when updating older issues for this tracker this will trigger an error message that this custom field is required. Fine, but this same error message is presented for all trackers, and as the custom field is invisible there is no way to update the issues.

I am using an old redmine version (pre 0.9, trunk 3171). I could not find a related issue so I do not know if this has been fixed already. Sorry in that case.


#1 Updated by Oskar Nordquist over 12 years ago

At first I could not reproduce this, until I figured out the actual scenario:

  1. Start with trackers Bug, Feature, Task
  2. Add an issue custom field for Bug that is not required
  3. Add an issue to Bug tracker with custom field unset
  4. Move issue to tracker Task
  5. Update issue custom field to be required
  6. Update issue will fail because it was previously on tracker Bug

#2 Updated by Go MAEDA about 2 years ago

I cannot reproduce with Redmine 4.1.

Also available in: Atom PDF