is there a way to selectively hide Linked issues field without use of scriptrunner in JIRA Cloud ?

[eleanor kerman]

Description of goal:

When cloning an issue to another project the cloned issue id is returned & added to the triggering issue in the linked issues field, is there a way to hide this from the customer/external user.

We have a custom text field similar to comments, we want to hide this also for customers but not from internal users.

We have customers who are able to register issues, thus they can follow the issues progress. we would like to filter which fields the customer will see. 

[Nic Brough -Adaptavist- · Accepted solution]

Jira does not have field security, so no, there's nothing you can do here.

[eleanor kerman]

OK

[eleanor kerman]

Does script runner (on JIRA CLOUD) offer solutions to hide a Jira field and a custom field ?

This is the bachground

When cloning an issue to another project the cloned issue id is returned & added to the triggering issue in the linked issues field, is there a way to hide this from the customer/external user.

We have a custom text field similar to comments, we want to hide this also for customers but not from internal users.

We have customers who are able to register issues, thus they can follow the issues progress. we would like to filter which fields the customer will see. 

[Nic Brough -Adaptavist-]

Not yet.  Cloud does not yet provide the framework or hooks for any app to make the front-end modifications that you're looking for

By the way, although you can do this with Behaviours on Server, the hiding is done by the browser, after the data has been given to it, so users can still view the raw html and see the data.  The work Atlassian are doing to enable something like Behaviours on Cloud looks to be similar - while it changes the front end and appears to hide the field, the users will still be able to see the content if they try.