Prevent Due Date from being Changed after it is created

[Amanda TAY]

Hi All, 

TIA. I want to create Epics and Tasks with due dates, but after it is set the first time I want to prevent it from being edited unless I trigger it by automation. What I have found though is that the due date cannot be input when I try to create a new issue if I turn the permissions to editing the Due Date off. 

How do I create it such that I can create new tickets with the Due Dates, but subsequently they will need to be edited by the automation?

Thank you,

Amanda Tay

[Valerie Knapp]

Hi @Amanda TAY , thanks for your post.

If you want to prevent the editing of the due date, it should be possible to achieve this by having the field only on the create and view screens for the issue type.

You can have also a workflow global transition to allow the editing of the due date using a transition screen. Here is the documentation for how to do this

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/ 

https://support.atlassian.com/jira-cloud-administration/docs/map-a-screen-to-a-workflow-transition/ 

I hope this helps you. Please let us know if you have other questions.

Cheers

[Amanda TAY]

Hi Valerie, 

Thanks for the quick reply. 

It will have to stay on the screen as people will want to see when the due date is. so removing the field from the screen is not an option. 

I am not getting how to set it up in workflows. Could you help with a bit more direction? 

The trigger is when a new issue is created, not a transition. 

Thanks again, 

AT

[Valerie Knapp]

Hi Amanda,

Thanks for your reply.

So, you can have an issue screen scheme like this, for each issue type, where you have different screens associated with the issue operations.

For example, I was suggesting you could have a configuration where the due date appears on the following screens

- Create

- View

But not on the Edit screen.

What that means is that when you are creating an issue, the field is there and you can add a due date. Then, once the issue is created, you can view the field but you won't be able to edit it, as it's not present on the edit screen.

You could then create another screen with just the due date on it, this is what I referred to as the transition screen.

In the workflow, you would need to create a global transition, then, when you click on the edit button, you can indicate which transition screen should be shown from the workflow transition.

In the issue, it looks like this

I hope this explains it better.

Cheers

[Amanda TAY]

Hi Valerie, 

Thank you, let me digest and test this and let update you!

Thank you!

[Amanda TAY]

Hi Valerie, 

I tried built and tested the solution, and created a new screen for "Editing" where i removed the "Due Date" field. 

- Tested: Create ==> Works

- Tested: View ==> Works

- Tested: Edit 

What i found is that when i trigger the workflow, it changes yes with the comment box pop up. But, I am still able to edit the Due date in the task. Do i have to create 2 screens for edit? And then how do i put them in?

[Amanda TAY]

@Valerie Knapp Hi Valerie, i am still having some issues, could you see my comment above please? Thank you!