Can we create project specific hidden (read only and editable by admin)field or metadata

[Vishal Kharde]

We have a requirement in which we need to store additional project specific details (meta data) like properties specific to a project. and this needs to only be editable by Admin of the project (read only for users/developers) and accessible through Validator/Rest API.
Can we use hidden field for such requirements and is there any plan to deprecate it in future from jira ?
Is there better suggestion to store metadata of a project?

Version: 8.5.1

[Daniel Ebers]

Your requirements looks related to a suggestion filed some years ago (https://jira.atlassian.com/browse/JRASERVER-2639). Unfortunately it was closed meanwhile (feature will not be implemented).

A hidden field could be a solution but you have to consider carefully if it causes some confusion when there are too many around.

Another idea that comes to my mind is the 'project description'. It is only editable by project admins and can be accessed via API.

Based on API documentation this endpoint should be a good start:
https://docs.atlassian.com/software/jira/docs/api/REST/8.3.2/#api/2/project

I came across a few use cases where it suffices to store/keep metadata in an external system, for example Confluence. In that case it is more a documentation and cannot be accessed through API like you described. It literally depends on your use case if this is an option at all.

Cheers,
Daniel

[Vishal Kharde]

Thanks for the suggestion, Daniel. I think Jira Entity property api will be more helpful here.