Is it possible to restrict users from changing data listed in tasks?

[Sherri Queen]

We assign tasks in projects to employees (users) with due dates to track their progress. As it stands now, the assignee can change the due date or assign the task to someone else. Is there a way to restrict this to only administrators?

[Trudy Claspill · Accepted solution]

Hello @Sherri Queen 

Are you working with projects in a Company Managed project or a Team Managed project?

For a Company Managed project, there is an Assign Issues permission in the Permission Scheme associated with a project. That permission is used to specify who can set the Assignee field in issues in that project.

The ability to set the Due Date field is based on the Schedule Issues permission.

A Jira Administrator can modify the Permission Scheme settings to change who is granted those permissiosns.

[Sherri Queen]

Ah! Thanks Trudy. I am working in a "Team Managed" project. Is it possible to change the restrictions within those settings?

[Trudy Claspill]

Based on this documentation it seems like you would be able to do that by creating a custom role with the permissions customized. The ability to set Assignee and edit Due Date are called out as distinct permissions.

[Sherri Queen]

I will take a look at it. Thanks. 

[Sherri Queen]

I have tried to create a custom role, but it doesn't appear to work. I also toyed with changing the project access and it still doesn't work. I tested many different scenarios today and each time, the employee was able to change the due date and assign it to someone else. 

Any other ideas?

[Trudy Claspill]

I can't really address why what you tried doesn't work without you providing the details of what you tried and then how it was tested.

What is the Access Level for the project?

What permissions did you allocate in the Custom Role?

What role(s) did you assign to the user that did the testing?

[Sherri Queen]

I apologize for not clarifying... I have tried different combinations, such as changing project to "limited" and creating a new role with the permissions I want to give. I then add the employee to the project and give him the custom role.

All looks good until I try to assign an issue to the person that I assigned the custom role. The system will not recognize this person. The system wants me to type in his email address, it then sends him an email inviting him to the project. I should not have to go through this each time I want to assign an issue to an employee that is given the custom role.  I hope that makes sense.

I have also tried creating a custom role in an "open" project access and that person is always able to change the due dates & assign the issue to another person.

Those are just a couple of the combinations I have tried. 

[Trudy Claspill]

In my own instance (I am using Jira Cloud Standard) I successfully

1. set a Team Managed Software project to Limited Access
2. Created a new role where I unchecked the Assign Any Issue and Edit Due Date permissions.
3. Assigned that role to a user in the project.
4. Ensured the user did not have any other role assigned.

Under those circumstances the user was not able to change the Assignee field nor edit the Due Date field.

Make sure that you have removed additional Role assignments for the user. The user will get the some total of all permissions granted in all Roles assigned to them. If one of there assigned Roles gives a permission that is not granted in another of their assigned Roles, the user will have the permission.

[Petr AST]

Hi @Trudy Claspill 

Can you please explain how it works for company-managed projects?

What should be done to limit the editing due date?

I see task scheduling, but when I turn off this permission for the role, the field disappears from the task. This is logical, but on view I would like to be able to see the due date field in this case.
Or am I doing something wrong?

[Trudy Claspill]

Hello @Petr AST 

The ability to modify the Due date field in a Company Managed project is governed by the Schedule Issue permission. That permission also governs a user's ability to change the Rank of issues and add issues to Sprints.

The details about what each permissions governs can be found here:

https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/#Project-permissions

[Petr AST]

Hi @Trudy Claspill 

Thanks for your answer

I checked again, yes, you are right, the field is available for viewing in this case, if it is filled.

This permission allows people to set or modify the value of the Due date field on your project’s issues.

But then it is not possible to create a due date if the due date is empty.

The idea is that the assignee can set a due date, and then only the administrator can change this field.

[Trudy Claspill]

Hello @Petr AST 

That is a different scenario than is outlined in the original question from the original poster. Please start a new Question outlining your scenario.