We have a start and end date in stories. What I want to achieve is - once a story is assigned to a sprint and set in-progress, users shouldn't be able to edit/change it. Or If anyone has better way to stop users from changing the dates once grooming/planning has been done. One way I got is to create a circular transition - is there any other solution?

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 lock a field in Jira after a certain state in workflow?

Smit Srivastava

We have a start and end date in stories. What I want to achieve is - once a story is assigned to a sprint and set in-progress, users shouldn't be able to edit/change it.

If anyone has better way to stop users from changing the dates once grooming/planning has been done.

One way I got is to create a circular transition - is there any other solution?

Accepted answers

Vishnukumar Vasudevan

Can be easily achieved if you have Script Runner plugin using its behavior module.

Follow below workaround if you do not have Script runner add-on.

1. Remove these fields from Edit screen and keep on View screen

2. Create transition screen and add these fields so that users can update these fields during transition.

3. Don't use the above transition screen once the planning is done.

All comments

Vishnukumar Vasudevan

Can be easily achieved if you have Script Runner plugin using its behavior module.

Follow below workaround if you do not have Script runner add-on.

1. Remove these fields from Edit screen and keep on View screen

2. Create transition screen and add these fields so that users can update these fields during transition.

3. Don't use the above transition screen once the planning is done.

Smit Srivastava

Hi Vishnu,

Thanks for the answer!

We don't have script runner plugins.

I am completely new to JIRA admin side, so excuse any silly questions/comments. I researched a little bit to perform the workaround you suggested - it seems to be lot of work considering the way Jira is configured/designed at my company.

But never mind thanks for the help!

Regards,

Smit Srivastava

Vishnukumar Vasudevan

Alright.

Welcome!

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

Quick Links

Find more posts tagged with

jira