nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

how to disable certain fields on an epic when it reaches a particular status?

Saad Ahmad_qeav55

Hello,

We have a situation where, when an epic reaches a certain status, we'd like to disable certain fields (e.g. Target dates).

This will help us restrict the edits & updates to certain information which is decided and added and later should not be altered.

Looking for native ways to handle it.

Accepted answers

Chitra Nagdeo

Hey @Saad Ahmad ,

Welcome to Atlassian Community Forum, My name is Chitra and I am part of Jira Cloud support team in Atlassian.

Please note Jira does not provide a built-in feature to make fields (here "Target dates") read-only or disabled based on workitem status (when an Epic reaches a certain status). However, there are workarounds you can use:

1. Screen Configuration Workaround

Remove the field from the Edit screen for the Epic issue type when it reaches the desired status. This makes the field uneditable in the UI, but it will still be visible in the View screen and can be set during creation.
To do this, create separate screens for Create, Edit, and View operations, and only include the field on the screens where you want it to be editable or visible.

2. Workflow-Based Workaround

You can configure a workflow transition (e.g., "Edit" transition) that is only available in certain statuses. The transition can use a custom screen that only includes the fields you want to be editable at that status. When the Epic is in the target status, users will not see the Edit button, but can use the workflow transition to edit only the allowed fields.

I hope these will help you achieve the necessary result, have a good day!

Thanks and Regards
Chitra Nagdeo

All comments

Chitra Nagdeo

Hey @Saad Ahmad ,

Welcome to Atlassian Community Forum, My name is Chitra and I am part of Jira Cloud support team in Atlassian.

1. Screen Configuration Workaround

Remove the field from the Edit screen for the Epic issue type when it reaches the desired status. This makes the field uneditable in the UI, but it will still be visible in the View screen and can be set during creation.
To do this, create separate screens for Create, Edit, and View operations, and only include the field on the screens where you want it to be editable or visible.

2. Workflow-Based Workaround

You can configure a workflow transition (e.g., "Edit" transition) that is only available in certain statuses. The transition can use a custom screen that only includes the fields you want to be editable at that status. When the Epic is in the target status, users will not see the Edit button, but can use the workflow transition to edit only the allowed fields.

I hope these will help you achieve the necessary result, have a good day!

Thanks and Regards
Chitra Nagdeo

Alexander Hohmann

In addition to @Chitra Nagdeo's answer, you could also create an automation rule triggered by field changes. When one of the considered field value is changed in a certain list of status, the action could replace the new value by the previous one, which it can extract from the smart value

{{#changelog.yourfieldname}}{{from}}{{/}}

It could also send a notification or email to the current user.

Maciej Dudziak _Forgappify_

Hi @Saad Ahmad

If the out-of-the-box workarounds aren’t sufficient for your needs, you might consider using the UI Modification API available for Forge apps. This API allows you to customize certain parts of the Jira UI, including hiding or modifying fields and interface elements.

You can choose to:

Build a simple Forge app yourself, tailored to your specific requirements, or
Explore the Atlassian Marketplace for free apps that already leverage this API and may cover your use case.