Is there a REST API available in Jira to show/hide custom fields specific to a Jira Project?

[Deleted user]

We are looking for any JIRA APIs available for hiding and showing custom fields specific to a JIRA project. 

We know there is a way to hide custom fields using Behavior functionality but we want to automate the process using a REST API. 

Please help us with the concerned issue. Thanks

[Deleted user]

Hi @Dirk Ronsmans 

Thanks for reaching out.

We are looking for ways to hide project specific custom field using a Jira plugin. We want to provide this functionality to Jira project admins so that we don't need to specify a behavior every time there is a requirement to hide a custom field. We were looking for any REST API that would help us in updating show/hide flag for custom fields. We are open to any other solutions as well as long as they don't involve writing behaviors every time.

Is there a way in which we can implement Behavior functionality for hiding custom field using Jira Plugin built on Atlassian SDK in Java?

[Dirk Ronsmans]

Hi @[deleted] ,

So you're trying to create a Jira app now? Going by your requirements you'd like to give the ability to hide/show fields towards a project admin. 

So sort of no-code behaviours to hide them?

i'm afraid that goes beyond my knowledge. You could also try asking this question at the Atlassian Developer community since it's about plugin development.

https://community.developer.atlassian.com

[Deleted user]

Hi @Dirk Ronsmans 

Yes we already are using behaviors to hide custom field for our clients but this involves too much manual effort. Thanks for sharing the link buddy. I will follow with developer community as well.

[Dirk Ronsmans]

Hi @[deleted] ,

I'm not sure what you are trying to achieve doing this with the REST api. A REST api interacts as a function to perform an action on the backend and it will return a result. 

A behaviour will interact with the frontend and hide/show/mandatory/.. items.

I don't see how a backend API call would be usefull to interact with custom field visibility..

Could you explain what exactly you are trying to do as a use case? (I'm puzzled)