Expand my Community achievements bar.

Join us LIVE in San Francisco on November 14th for Experience Makers The Skill Exchange. Don't miss out on this free learning event!

Copied Tasks take on New Project Permissions

Avatar

Level 4

4/24/24

Description - When users copy tasks from an old project with assignments, if they don't choose to carry over the old projects permissions the task in the new project does not give any permissions at all. I would have expected this task to take on the task permissions set on the new project but WF support says this is not the intended behavior.

Why is this feature important to you - Our PMs often copy sections of tasks from previous projects to save time, but they do not realize that the new task doesn't give any permissions. When the task assignees try to interact with the task they are met with no access errors.

How would you like the feature to work - I would like any task copied from one project (if permission is not selected to copy with it) to take on the task permission set on the new project.

Current Behaviour - Currently the task copies over but no permissions are given to the assignees for the task or project

5 Comments

Avatar

Community Advisor

4/24/24

hi, I'm not sure if you read the documentation or not?

https://experienceleague.adobe.com/en/docs/workfront/using/manage-work/tasks/manage-tasks/copy-and-d...

 

The Permissions toggle will leave or remove the names of everyone shared on the task. The task in the new project should at least be giving "inherited permissions" regardless of what you do to this toggle -- if you feel like you're not even getting that line, you should check your project's Access settings.

Avatar

Level 4

4/24/24

Yes, we were not selecting Permissions because we did not want to carry over the permissions from the old project. Our New project is set up to give contribute access to the Task and view access to the Project. But when you copy without checking permissions in the old project, no permissions are granted in the new. I expected it to inherit the permissions of the new project but WF support told me this is performing as expected and to put an idea in to request it behave the way I expected it to.

Avatar

Community Advisor

4/24/24

Can you be a bit more clear (like giving a real life example)? e.g.

 

In Project A, a task is shared with John Smith. The task by default also has inherited permissions.

 

* When you copy the task to Project B, and you click Permissions off, the task will be copied and not shared with John Smith. The task will inherit permissions from Project B -- this is the inherited permissions line -- whoever is shared to Project B will be able to see the task. Through Project B Access settings, if you have it set up correctly, everyone assigned to this task will be able to see Project B as well.

 

* When you copy the task to Project B, and you click Permissions on, the task will be copied and explicitly shared with John Smith. The task will inherit permissions from Project B -- whoever is shared to Project B will be able to see the task. Through Project B Access settings, if you have it set up correctly, everyone assigned to this task will be able to see Project B as well.

 

What is it that you're seeing instead of this?

Avatar

Level 4

4/24/24

I am copying a task from Project A that is assigned to Edit Test, and Test PM User. I deselect permissions as we don't want to copy the permission they had to this project and instead want them to get the permissions set up in the new project.

 

Project B is shared with 2 users. Once this task is copied to this project, it comes in assigned to Edit Test and Test PM User. The 2 users that were shared on the project inherit access to the task, but the 2 users that are assigned to the task do not get any access to the task or the project. If I assign a new user to this task they get the permissions in the project details but the 2 users that were assigned and copied with the task do not get any access.

Avatar

Community Advisor

4/24/24

I think I get it. Without actually going to the trouble of testing it in my system, my initial assessment is that the permissions at the TASK level have nothing to do with the project. If you click on the "share" a task with John Smith, there's no way to say on that sharing, that John should also have manage access to the project. I would suggest just leaving permissions toggled on.