Can we make a field required for an exiting issue type in jira project

[Diana Meethalai Puthiyedath]

We currently updated a field required for Issue Type = Bug in one of the project but this change is not reflecting to the existing Bug types created prior to this to new change. Is there a way to prevent users on saving those issue types when they try to update the existing bugs.

[Hector Florin · Accepted solution]

Hello Diana,

I see the problem. For existing issues, the required field can remain empty as long as it's not updated, as if is it cannot be removed.

However, the users can still update the other fields and leave the new required field empty.

That's a problem indeed. 

Why would you need to prevent users from update those tickets? Could it be to keep those tickets as archives, so you want to treat them as read-only issues?

The answer is still quite tricky, and here is what I've found on that 

https://community.atlassian.com/t5/Jira-questions/how-to-make-a-custom-field-read-only-when-my-issue-transitions/qaq-p/1835279#:~:text=1%20answer&text=Good%20point%2C%20but%20it's%20still,a%20screen%20that%20includes%20it.

I hope it helps.

Thanks,
Hector

[Diana Meethalai Puthiyedath]

Thank you. My issue is. 

We made few fields required in the new defect workflow. But this new required field change is applying to only for the new bugs. We wanted those fields to be required for the existing bugs as well so when user tries to update that bug it forces the user to enter all the new required fields. 

Is there a way where we can stop users while saving the existing bugs(when they do some edits) without entering the required fields?

[Hector Florin]

Hi Diana,

Thank you for your details.

I'm afraid there is no way for the moment. On all my tests, a user is always able to update the fields on the old bug tickets that had the required field empty.

Until there is no way to disable the fields in the view screen we cannot make that to happen.

Thanks,

Hector