How can I prevent the particular field to be edit on a resolved or closed issue?

[Ruhi Tanwar]

I want to put restrictions on particular fields. On resolved and closed tickets, no one can edit those fields. means If the ticket status is resolved or closed, then that particular field (default field, which provided by Atlassian) will not be available or editable.

I want the "Time Spent" field in the "Time Tracking" section on a closed or resolved ticket should not to be editable.

I know that some fields are not editable if those fields are removed from "Edit Screen", but this is the default field and I need help.

[Nic Brough -Adaptavist-]

So for most fields, the answer is "you cannot do this" - you can make an issue editable or not with properties on the workflow status, but it's the whole issue - all the fields or none.

However, you are looking at the time-tracking, which is not an issue field, and it does have permissions.  

So https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ covers the general principle you need here - if you put workflow properties on to your resolved and closed status, you can change the permissions when the issues reach that point.  And time-tracking has its own permissions.

Breifly though, if you put on a property like this:

jira.permission.work.group=jira-administrators 

means that only Jira administrators can log work when an issue is in this status (log work is a part of the time-tracking functionality, as is "time spent", so this should stop all changes to the time-tracking stuff).

I've emphasised the work there because that's the main variable - the docs cover other things you can change the permissions for, and you may want to look at how to kill off delete work log, edit work log and so-on.

[Ruhi Tanwar]

Hi Nic,

I tried this, but it is not working. I do not know why is this not stopping work, I put it on the property at the resolved status.

[Daniel Ebers]

@Ruhi Tanwarthere are "Transition Properties" and "Step Properties". It seems you have assigned the value to the wrong one :)

When clicking on a step in workflow diagram you can assign a property to a step - it should work then.