Context: Our roadmap planning process in JPD is highly collaborative and involves multiple departments (Product, Engineering, Design, etc.). Currently, all of our contributors are set up as "Creators" to allow them to contribute ideas and views.
Problem: While we want broad collaboration, specific departments own specific data points. For example:
PM Team: Owns the "Impact" score.
Dev Team: Owns the "Effort" score.
Because everyone is a "Creator," everyone has edit access to all fields. This frequently leads to inadvertent updates where a team member accidentally changes a value they shouldn't be touching. We are struggling to maintain data integrity across these cross-functional fields.
Ideal Solution: We need the ability to set field-level permissions or "lock" specific fields based on user roles or groups.
Ideally, this would function similarly to how we can currently "Lock Views" in JPD Premium where we could have a field be viewable to all but limit edit access to specific team members.
Has anyone found a workaround for this, or is this on the roadmap?
Hello Jena, Jira Product Discovery projects are based on team-managed projects, which is a concept shared accross Jira, Jira Service Management and Jira Product Discovery.
Today, team-managed projects do not support field-level permissions, and it is not currently on the roadmap.
Best regards,
Hermance
What about for contributors?
We want contributors to see status (among other fields) but not change the status by mistake. If we cannot restrict fields, then it would be very beneficial if there was a proper view-only permission that can be applied to lists or board views where contributors can view fields but not change the vote/rating/status.
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.