Get product advice from experts

Ask a question →

Join a community group

Find a group →

Advance your career with learning paths

Take a free class →

Earn badges and rewards

Connect and share ideas at events

See the calendar →

Community
Products
Jira
Advanced planning
Questions
Portfolio plug-in allows editing of read-only fields (in Jira Server)

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

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?

7 answers

1 accepted

0 votes

Answer accepted

I'm using this plugin and I have noticed this problem. I ask you to give more importance to this issue as this is also a major security issue. If you use a Security Level based on a user picker field, and this is editable by anyone with Advanced Roadmap it is possible to make visible issues that normally would not be visible on JIRA. Advanced Roadmap overrides any controls that are set in JIRA.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

4 votes

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?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

1 vote

Vote for this to be fixed!

https://jira.atlassian.com/browse/JPOSERVER-3108

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

0 votes

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

0 votes

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

0 votes

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?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Reply

0 votes

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like

Reply

Suggest an answer

Log in or Sign up to answer

Was this helpful?

Thanks!

Advanced planning

TAGS