how do you restrict who can edit certiain fields in jira?

[DI IELSI Carol]

We are currently using Tosca and will be installing a  middleware product (Tasktop) to enable Jira and Tosca to communicate and stay in sync for; Epics, User Stories, and Issues.

 A number of the fields we want to be owned by Tosca (Created and Updated) but not editable by the project users in Jira. Is this possible?

thank you!

[Nic Brough -Adaptavist-]

You do not.

There are some system fields that are controlled by permissions in Jira (scheduling, security and can-assign issues), and there are fields that are simply not editable at all, but for the rest of the fields, the choice is binary - you can edit the issue, or you can not.

The two fields you mention fall into "not editable".  Created is filled in as the issue is created.  Updated is calculated from the last issue change. 

That also means that the idea that "Created and updated are owned by Tosca" is nonsense.  Jira will handle them because they're based on things happening in Jira.

[Jonny Adams]

@DI IELSI Carol You can edit permissions for the project in Jira. Just remove users from the Edit Issues permission.