Read Only Custom Field

[rsstorey]

I have a requirement to have some read only custom fields within one of my Jira projects.  This Jira project is integrated with another 3rd Party tool.  The specific function of the integration is:

1.  Pass key identifying fields from Jira to the 3rd Party tool to create a record based on the Jira issue.  All of these fields in the 3rd Party tool are read only except when passed via the API from Jira to the 3rd Party tool

2.  When the 3rd Party tool creates the record is assigns two required read only id fields that need to be passed back to Jira and populated into two custom fields that cannot be edited by any user.

This allows traceability between the Jira issue and the 3rd Party record.

I've tried to remove these custom fields from the create screen but it needs to be in the view screen but it can still edited.  I would like these custom fields treated somewhat like the Jira Key field that can only be edited by via the API.

Appreciate any suggestions on how to 

[saulo fonseca]

Hi @rsstorey .

The operations: Create Issue, Edit Issue and View Issue are associated with the same screen?
For example: 

You can create a different screen for each operation, so you will associate the field where it really should belong. For example:

Operation                Screen
Create                       Screen1
Edit                           Screen2
View Issue                 Screen3

I have the custom field called CF1 and I just want it not to be editable, so I must associate it with Screen 1 and Screen 3.  Did you understand?

I look forward to your reply.

[rsstorey]

I think I do understand.  I'll will give this a shot and test it.  Thank you.

[rsstorey]

Follow on question:  Although I don't want the fields to be edited, I do what to be able to create issue links from other projects that do need to be reflected in this project's issues.   So do I need to do anything with the issue's links?