Jamie, that looks like a valid token. What does "with no luck" mean? You added that token to the WFS and a stakeholder can't see the buttons? Did you also give that token "edit" rights on the request type?
In testing this change, I assigned myself as the Project Manager on the Associated Project for a given Project Issue. More specifically, I should see buttons to Reassign, Close, or Escalate the Issue, but the buttons are not visible, indicating to me that my token in the Workflow Security tab for that step is not working correctly.
I did not try adding that token on the Request Type security - I'll try that as well.
The only other thing that's suspicious is that the Associated Project on the request is using a custom validation. The validation returns ProjectId (hidden), ProjectName (displayed), and ProjectId (displayed).
Maybe this is the culprit?
It appears to be modeled after the standard "PMO - Master Projects" validation. The Associated Project field is using the KNTA_MASTER_PROJ_REF token.
you told you changed the field in project request and use the token in the project issue workflow. What does the approval details of the project issue say. If it shows your name, the token ist fine, otherwise ... But the token security is not that dynamic. It's calculated and stored in database on save. So if you changed the stakeholder and didn't save the project issue again, the approval details will show the right user although you won't have permission.