You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have an object schema from tracking equipment. It is in a tree with object types hierarchy. The final objects can have multiple attributes. We want users to be able to view all attributes but edit only certain attributes. What is the best way to do it?
Can we create another schema that references the original schema but has only the attributes that all users can edit? So that a user can the object in first schema, has an attribute pointing to the object in another schema where the user has permission to edit the attributes that are referencing the original schema. Once the edit is made, will it be reflected in the original schema too?
The way we've solved this (and it's not necessarily optimum) is to create a Jira project which allows for the creation and editing of objects via normal issue workflow transitions. Basically, creating a separate interface.
The perk of this is that you can restrict a user to only edit particular objects and particular attributes.