Field-Level Permissions / Ability to Lock Specific Fields

[Jena Miller]

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?

cc: @Regina Whyte @Sharon Connell