I think the Temporary Signature Authority functionality may handle this for you. Take a look at the GSM User Guide for details. Here is a snippet:
Temporary signature authority enables a person who has been asked to provide a signature to assign that task to another user. A user with temporary authority can view and advance or move back all signature documents that are currently owned by the original signature authority. Tasks assigned to a user with temporary authority also appear in the Action Items list of that person.
I think temp signature authority could work for us when the task owner knows they need to re-assign. However, that is not the majority of our use cases. We actually need the owner of the status in the workflow to be able to re-assign the task and not the actual person who was assigned it. There are many times where users switch brands, go out of town and don't inform the spec approval team, etc. So we need to be able to re-assign tasks as workflow owners/admins to different users.
Is there a way to do this today in 6.1.1?
For GSM Signature Documents, a user with the [TSA_ADMIN] role can assign a temporary signature authority from users (including users other than themselves) to other users. This is an administrative role, meaning it shouldn't be granted to just anyone. So if Kelly had the TSA_ADMIN role, she could allow Sally to sign off on signature documents for Bob. That means that the relevant signature documents would show up on Sally's action items, and she would have permission to workflow (sign off) the Signature Document.
This does not cover spec ownership, however, just Signature Documents.
Is this what you are looking for?
Not exactly, giving TSA would work in certain situations. However, we need the ability to re-assign individual tasks within a workflow. We wouldn't always want the person given TSA to receive all tasks for the original owner, but rather we need the ability to pick and choose which tasks get re-assigned.
OK, thanks for the clarification. So no, there is no way to currently do this in the application without a re-workflow.