Defect #14496

Permission check on an unused custom field leads to unwanted restriction for the ticket status

Added by Jürgen Diez about 5 years ago. Updated almost 5 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Category:Permissions and roles
Target version:-
Resolution:Invalid Affected version:2.2.0


We have several project with different custom fields.

For these custom fields we defined rules where it is required for a certain status.

However for some projects these custom fields are completely irrelevant and therefore deactivated in the project configuration. Now these field are not available in these project.

The problem is that we can't set the status of the ticket now, because the field is not available in that project but required in the projects where it is used.

The permissions for custom field should be changed to be checked only if a custom field is selected in a project.


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

  • Status changed from New to Needs feedback

I can't reproduce with current trunk.

The problem is that we can't set the status of the ticket now

Could you describe what happends exactly?

#2 Updated by Jürgen Diez almost 5 years ago

Hmm... I can't reproduce it either.
I guess it was a mistake in my configuration.

I think you can close this ticket.

#3 Updated by Etienne Massip almost 5 years ago

  • Status changed from Needs feedback to Closed
  • Resolution set to Invalid

Also available in: Atom PDF