cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

Enable possibility to assign tasks directly to groups or multiple users

Enable possibility to assign tasks directly to groups or multiple users

When you create or edit a change task you cannot select a group or multiple users as "Assignee" or as "Reviewer".

You can only choose a single user.

This should be possible and enabled.

After you finish the "Create Change Task" or the "Edit Change Task" wizard and you open the "Process" tab in the change task you are able to add / choose a group or multiple users.

Why is this not possible before when you are in the "Create Change Task" or the "Edit Change Task" wizard?

We know the possibility with the participant list table (see PTC Techsupport Document https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS125788 and also Product Idea Allow Individual Users Within a Group to be Selected for Workflow Task Assignment with Setup Participants) but why is it not possible with the participant search function in the "Create Change Task" or the "Edit Change Task" wizard?

The participant list table unfortunately covers not all use cases. If you want to assign the task to users or groups which are not members of defined roles for the tasks or which are not members of the context team it´s not possible. With the "Find Participant" wizard it would be possible.

EngineeringChangeTask_User_Group_selection.png

5 Comments
JeffZemsky
17-Peridot

The ability to Add Multiple Assignee/Reviewer was added in Windchill 10.1 M040 and in Windchill 10.2 M030 we added support to define Resource pools directly from Team Roles, rather then from the whole team.

You can find information here:

https://support.ptc.com/cs/help/windchill_hc/wc110_hc/index.jspx?id=ChgMgmtChangeTaskParticipantListTable&action=show

and here:

https://support.ptc.com/cs/help/windchill_hc/wc110_hc/index.jspx?id=ChgMgmtParticipantListEnable&action=show

Here are some examples

Video Link : 7877

dritter-3
12-Amethyst

Hello Jeffrey,

I explained the blocking point why I created this product idea a little bit better in the description:

"The participant list table unfortunately covers not all use cases. If you want to assign the task to users or groups which are not members of defined roles for the tasks or which are not members of the context team it´s not possible. With the "Find Participant" wizard it would be possible."

Please change the status from the product idea so that the people can vote again.

Thank you.

dritter-3
12-Amethyst

This would fix also following problem:

Some situations in the system cause an accidental removal of already accepted tasks and / or a reassignment of tasks.

Some examples:

  1. Example: Change Task Members table > Role "Assignee" is filled with 1 group
    • As long as a group is assigned to the CT process role "Assignee", the Assignee field in the CT edit wizard is empty (if you do "Action > Edit").
      Then you have to add a Assignee manually in the CT edit wizard to be able to finish the CT editing.
      This will assign the "Complete Change Task" to the Assignee chosen in the CT edit wizard (no matter if somebody else has already accepted it).
  2. Example: Change Task Members table > Role "Assignee" is filled with 2 or more persons
    • If 2 or more persons are assigned to the CT process role "Assignee", the Assignee field in the CT edit wizard is filled randomly with one of these assignees (if you do "Action > Edit").
      The person who edits the task has to check which assignee is shown in the CT edit wizard, because
      finishing the CT edit wizard will assign the "Complete Change Task" to the Assignee shown in the CT edit wizard (no matter if somebody else has already accepted it).
DomenicLaritz
16-Pearl

@PTCModerator, why does this idea have no status?

PTCModerator
Emeritus
Status changed to: Acknowledged

Good question. This idea should have been marked as Acknowledged. Thanks @DomenicLaritz !