@AngelinaIgnatova, thanks for the insight into locked custom fields. Indeed, internally we thought about this as a possible solution for App Access rules in regards to custom fields. Then at least it’s relatively clear to end-users, that a custom field “belongs” to an app, and indeally which app.
So far, so good.
But: I don’t see how we as an app can:
- create locked custom fields
- update an existing custom field as locked by our app
I did found this docu where it says:
When you install a Jira product or plugin, some fields that are needed by that product or plugin are created and locked.
(I assume that “plugin” means “app” here. Correct me if I’m wrong.)
But I don’t see in any docs and/or the REST API how to actually do this as an app. Can you help here?
Thanks.
Andreas
PS: I don’t see locked custom fields mentioned on the subsequent RFC-29. Is that intentional (because out-of-scope), or because you don’t want to duplicate the topic? Just curious.