Status property prevents assigning to user on transition screen

[Marcel Plomp]

To specific workflow statuses we added properties so issues can only be assigned to users having a special role (developers) when the issue is in that status.

If we want input from a Team member (not being a developer) we have a transition "Ask for input" with a screen to assign the issue to the person we want input from.

As this person is not a developer we cannot assign the issue to him/her (on transition) as this is prevented by the property of the current status.

In the next status (Waiting for input) the Team member has the assignable user permission.

So the workaround is: 1) do the transition, 2) Assign to the team member.
But we would like to do this at the same time.

Why is the current status property blocking the assign option (for a team member) on the transition screen? And how can we solve this?

[Nic Brough -Adaptavist-]

The property blocks it because until you finish the transition, the issue is still in the status with the property on it.

There's no workaround without code really, and even that's a bit clunky.  If you add a new custom field for "next assignee", let them fill it in on edit, and then copy it into assignee in a post-function (and maybe blank out the "next assignee")

[Marcel Plomp]

Forget it......made a little mistake.

The name of the new assignee does not show up in the assign field (not selectable from a user list), but the transition can be done when you enter the correct user name manually.