Defect #17744

Disabling fields in tracker keeps attached workflow permissions

Added by Etienne Massip over 8 years ago. Updated about 8 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:


Category:Issues workflow
Target version:2.6.1
Resolution:Fixed Affected version:


Say e.g. you create a tracker by copying an existing workflow for which some field permissions have been specifically set.

Deselecting the fields used by the tracker (at creation time or at a later time) doesn't remove these permissions.

The may lead to some Version Id can't be blank error message at issue form status update if the original workflow stated that the field is mandatory for the new status even if the Version Id field is not in the form.

This is not easy to determinate as the workflow permissions are not visible in the administration screen but only in database.

Associated revisions

Revision 13557
Added by Jean-Philippe Lang about 8 years ago

Fixed that a disabled field which is required by workflow rules blocks issue creation/update (#17744).


#1 Updated by Jean-Philippe Lang about 8 years ago

  • Status changed from Confirmed to Resolved
  • Assignee set to Jean-Philippe Lang
  • Target version changed from Candidate for next minor release to 2.6.1
  • Resolution set to Fixed

Fixed in r13557. The rules are not removed but the validation now takes of disabled fields.

#2 Updated by Jean-Philippe Lang about 8 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF