The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.
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.
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.
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.
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.