Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

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

NAYANA
NAYANA Jul 16, 2020

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?

Answer
Watch
Like Be the first to like this
643 views

7 answers

1 accepted

0 votes
Answer accepted
Antonio Bosio
Antonio Bosio Dec 22, 2021 • edited

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.

Reply
4 votes
nayanageddam
nayanageddam Feb 12, 2021

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? 

Reply
Reply
0 votes
Jana Pelz
Jana Pelz Jun 28, 2021

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

Reply
0 votes
NAYANA
NAYANA Jun 09, 2021

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

Reply
0 votes
NAYANA
NAYANA Mar 29, 2021 • edited

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?

Reply
0 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Jul 16, 2020

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

View More Comments
NAYANA
NAYANA Jul 16, 2020 • edited

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?

Like
Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced planning
TAGS
AUG Leaders

Atlassian Community Events

See all events