Edit due date only by Project Lead or Administrator role

[Yury Ked]

Hi everyone!

I made nexts steps to achieve the goal.

create 3 types of screens:

And remove field "due date" from Edit and View screens. Thats cool and now noone can change date after issue created.

The next step is allow to edit date for Administrator or ProjectLead.

I've create new screen with date field only and edit workflow like this:

And setup condition:

But I cant edit due date as Administrator anyway.

Could you pls suggest to me whats wrong?

Thanks a lot!

[Pasam Venkateshwarrao]

@Yury Ked Adding one more solution.you can remove the due date field in Create screen and add a post function in workflow at starting.

refer the image

In Lookup group add the administrator.

[Pasam Venkateshwarrao]

@Yury Ked You can add the due date field only in View and edit screens , run this automation rule

[Yury Ked]

@Pasam Venkateshwarrao hi dear friend!
I've created that automation: but reporter (person who is created issue) can edit due date field without admin permissions anyway. Smth missed?

[Vignesh Jayagopal]

Hi @Yury Ked  We had a similar requirement, and instead of removing the field from the edit screen, we restricted editing using status properties. This approach worked well for us. You can try the same and refer to this detailed overview on status properties in the link below.

https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status 

[Yury Ked]

Hi @Vignesh Jayagopal I add that rules for "IN PROGRESS" status for test. But anyway reporter can change due date(

[Vignesh Jayagopal]

@Yury Ked Could you try deleting the property for the reporter and test again? Also, please ensure that the reporter is not assigned an admin role or set as the project lead.

[Yury Ked]

@Vignesh Jayagopal Sure my friend

For test purposes I've created a new user without admin or project lead permissions.

And the result the same: reporter can edit due date in "IN PROGRESS" field anyway.

[Vignesh Jayagopal]

@Yury Ked

It worked well for us, need to spend some time on this to see why this is failing for you.

Can you try deleting the jira.permission.scheduleissue.reporter property and keep only the two properties for Lead and Administrators?

This way, only the Lead and Administrators will have permission to edit the due date, and no one else will be able to do so.

[Yury Ked]

@Vignesh Jayagopal sure my dear friend.

And reporter still able to change due date anyway.

The problem is could be in permissions?

But if i remove reporter from it, it will be unable to set due date when task creating any user(not admin or project lead), and field due date is required for task creating. 

The goal - that any user can create task and due date is must, but after task created - only admin or project lead can change due date.

[Vignesh Jayagopal]

@Yury Ked 

No need to remove the Reporter from the permission.

It's strange—I have the same setup, and it's working fine for me.

Are you testing with the issue status set to In Progress? This restriction only applies when the issue is in the In Progress state as you have added the property in that status, and the Reporter can still edit the due date in other statuses.

[Yury Ked]

@Vignesh Jayagopal yes TU - is the test user

Than create task

Than edit due date

And just reporter without admin&project lead permissions can change it

[Vignesh Jayagopal]

@Yury Ked This should be working, Please reach out to Atlassian support to check what is missed here.

[Trudy Claspill]

Hello @Yury Ked 

Do the specified roles have the Schedule Issues permission in the Permission Scheme associated with the project?

[Yury Ked]

Hi dear friend!

Yes.