I want to make some custom fields in Jira Tempo readonly. Is there a way to achieve this?

[Kiriti Kantamneni]

I want to make some custom fields in Jira Tempo readonly. Is there a way to achieve this through Jira Configuration.
Or is it possible through any of jira's behaviours or any other way to make some of these custom fields un-editable.

[Layssa Souza]

Hi, @Kiriti Kantamneni 

There are a few approaches to this scenario.

In Jira Cloud, since ScriptRunner Behaviors is not supported, the best solution to make Tempo Timesheets fields read-only would be to use a combination of:

1. Jira Automation (Jira Automation)
You can set up an automation rule to roll back unwanted changes to a custom field. This does not prevent editing directly, but can ensure that any changes are automatically undone.

Steps to create the rule:

- Go to Settings → Automation in Jira.
- Click Create rule.
- Choose the trigger: "Field Edit" or "Issue Edit".
- Add a condition to check if the edited field is the one you want to protect.
- Add an action to revert the change (for example, restore the original value).
- Save and activate the rule.

2. Restriction via Time Permissions
If your goal is to prevent editing of time logs after registration, you can configure permissions in Tempo Timesheets itself:

- Go to Time → Settings → Permissions.
- Configure rules to prevent users from editing time entries after a certain period.
This doesn't lock individual fields, but it can prevent users from making unwanted edits.

3. Jira API + Tempo
If you need a more robust solution, you can create a custom automation with an external script via Jira REST API + Tempo API to monitor and roll back changes to the desired fields.

I hope this can help you.

Best Regards.