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; } } }

Locking the "Procurement Strategy Type" Field After Value Selection in JWM

Seenivasan K

In my JWM project, I have a dropdown field called Procurement Strategy Type with three options. When a value is selected, Jira Automation automatically creates the corresponding subtasks. However, if an incorrect value is chosen and later corrected, subtasks for both the incorrect and correct selections remain.

Now, I need to lock the field after a value is selected so that it cannot be edited further. Is this possible, or would you recommend an alternative solution that better suits my requirement?

Screenshot 2025-02-25 131117.png

Accepted answers

All comments

Rilwan Ahmed

Hi @Seenivasan K ,

Welcome to the community !!

There is no direct way to do this. Workaround is

Make Procurement Strategy Type required/mandatory during the ticket creation and remove the field from Edit screen. This will force users to select field only during the ticket creation and make uneditable after that.
Make use of workflow properties like
jira.issue.editable --> To make an issue editable when it's on a particular status
jira.permission.edit.denied --> To disable editing when an issue is on a particular status, for all users including admins

More details about workflow properties is in https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

Stephen.Lugton

Hi @Seenivasan K

Jira issues can have 3 screens associated with them; Create, Edit and View:

Create Screen: Used to create the work item with a defined set of fields available
View Screen: A view that shows the fields associated with a work item
Edit Screen: Used to edit / update existing fields

You can use the same screen for all three operations (create, edit and view) or you can have different fields available on each screen.

In your case you could have the Procurement Strategy Type field available only on the Create and View screens (making sure to set it as a mandatory field)

See https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/ for more information on screens

Seenivasan K

Hi @Stephen_Lugton

Thank you for your prompt response. The solution you provided does not fully address my requirement. The Procurement Strategy Type field is not available on the create screen because it is generated automatically through automation.

To clarify further, our project structure consists of four levels:

Level 2 Epic
Level 1 Epic
Story
Subtasks

As per our project requirements, when a Level 2 Epic is created, all associated Level 1 Epics, Stories, and Subtasks are generated automatically through automation. The dropdown field in question is located within the Story-level issue. Since the Story-level issues are created automatically, it is not feasible to add this field to the create screen. Additionally, adding this field to the Level 2 Epic screen is not an option, as it belongs to the Story level.

Seenivasan K

Hi @Rilwan Ahmed

To clarify further, our project structure consists of four levels:

Level 2 Epic
Level 1 Epic
Story
Subtasks

Pasam Venkateshwarrao

Hi @Seenivasan K

Thanks for reaching out to the community

This is describe in the answer from Vera on this post

Unfortunately, Atlassian does not offer field level security. The only way you can accomplish this natively is:

Remove the fields from your Create/Edit screens
Create a new screen with the desired fields
Add a new status (e.g. Update Fields) to your workflow

This approach will give those with the appropriate role the ability to transition to a new status which will prompt them to fill in your desired custom fields.

Stephen.Lugton

Will the Procurement Strategy Type be the same for all the story-level issues under a Level 2 Epic?

Seenivasan K

No it's for only one story level

Pasam Venkateshwarrao

@Seenivasan K have you tried this?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud