How to Lock Start and End Dates After Transition in Jira Automation?

[Naveen Kumar Gangula]

Hi everyone,

I'm currently working on setting up an automation rule in Jira to manage change requests. Specifically, I want to ensure that once a change request moves from the "Approval" stage to the "Implementation" stage, the Start Date and End Date fields cannot be edited by any user.

Here’s what I’ve done so far:

1. Created an automation rule with the trigger Issue Transitioned from "Approval" to "Implementation".
2. Tried to add an Edit Issue action to set the Start Date and End Date fields to their current values using smart values like {{issue.Start Date}} and {{issue.End Date}}.

However, I’m unable to find the Edit Issue action in the list of available actions. I’ve checked my permissions and field configurations, but the action still doesn’t appear.

Could anyone guide me on how to:

1. Ensure the Edit Issue action is available and correctly configured.
2. Lock the Start Date and End Date fields so they cannot be edited after the transition.

Any help or suggestions would be greatly appreciated! Any other ways to do it is also appreciated.

Thank you!

[Walter Buggenhout]

Hi @Naveen Kumar Gangula and welcome to the Community!

With a recent change of terminology in Jira, look for edit work item instead. It is the same action, but with a new name.

I don't quite understand, though, what you are trying to do with setting the values for start and end date to "their current values". Probably, I am misreading your question somehow, but as you are describing it, you are updating the value of this fields with the value they already have ... that seems like an unnecessary action, no?

If you have start and end date as fields on a screen associated with the workflow, you can restrict editing of those fields afterwards - at least if you're working with company managed projects. Just make sure the fields are only on the view screen in your project and not on the edit screen. That would make them viewable, but not editable (except through the transition you mentioned earlier).

There's a caveat, though. If you want to set these fields through an automation rule, they need to be on the edit screen as well. And in that scenario, you won't be able to restrict editing afterwards either.

Hope this helps!

[Naveen Kumar Gangula]

Hi @Walter Buggenhout , thanks so much for the warm welcome and your helpful explanation!

Ah, that makes sense now—“Edit work item” being the renamed version of “Edit Issue” clears up my confusion. I’ll update the rule accordingly and give that a try.

My requirement is :

When i am trying to transition the Change in my Change management project from Approval to Implementing/Will be implemented. My requirment is the other people should not change the start date and the end date.So i want the start date and the end date should be readable only. 

I really appreciate your suggestion about using different screens in the workflow. I’m working in a company-managed project, so just to confirm:

If I remove the Start Date and End Date fields from the Edit Screen, but leave them on the View Screen and the Transition Screen, that would allow the fields to be set during the transition and viewed later but not edited—is that correct? Can you elaborate more  or share some links how i can acheive this

Thanks again for your guidance!

Best,

Naveen