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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
In our upcoming implementation of JSM Insight there is a desire to provide permission to some users for editing the attributes of existing objects but not to allow them to create new objects. That object creation could be provided to another higher level set of users. But at this point it looks like the schema developers role provides both create and edit of objects. Is there a way to work around that combination of create and edit permission in one role?
I see on the Atlassian Suggestion Dashboard someone has suggested this feature for Server however I cannot see one for Cloud.
I would recommend submitting a case to Atlassian to get this functionality added for Cloud:
I had a look through the asset permissions tickets but couldn't see any kind of suggested workaround unfortunately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.