Portfolio plug-in allows editing of read-only fields (in Jira Server)

[Nayana Geddam]

Portfolio plug-in allows editing of read-only fields. A custom field that was made read only in Jira is editable in Advanced roadmaps and this is circumventing controls. how can we fix that?

[nayanageddam]

This is huge an issue. the workflow controls, custom fields controls validations do not apply in advanced roadmaps. The Plans simply allows users to circumvent all of the business rules and poses a gaping hole for data integrity issues. is there a way to make fields read-only or restrict certain operations based on roles in advanced roadmaps? 

[Nic Brough _Adaptavist_]

How are you making the fields read-only in plain Jira?

[Nayana Geddam]

If it is read only unconditionally, we simply remove it from the create/edit screen. If there are only a few cases where it is read only then we use behaviors. 

Tried disassociating all the edit screens to the custom field. It is still editable in Advanced Roadmaps(3.29). 

Same issue was observed in other versions as well. Is there a way Advanced Roadmaps allows to set a field as read-only on the plan view?

[Nayana Geddam]

Following up on this questions - is there a bug fix available. to retain read only Jira fields as non editable fields in the Advanced Roadmaps plug-in as well?

[Nayana Geddam]

Hello, Any updates on this query? Is Atlassian considering providing the ability to restrict editing fields in Plans?

[Jana Pelz]

Same problem here! This bug is needed to be fixed urgently. All ideas in regard to role & permission management are obsolete.