You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I had try this with automation-for-jira-3.14.0 and it works for one project and for another project it didn't work. The interesting thing is that the configuration of these two projects are just like each other.
As informed by @Adam Rypel _MoroSystems_ it is impossible for the user to get the issue assigned without having the permission from what i can remember . At least for the user to get the issue assigned to him ,he needs to have been added to assignable user permission .
One more thing ,about the rule . Because the issue creator is the one to whom the issue should be assigned . So he should have the assignable permission .
If i could think of a workaround maybe create a component as Other creators and add the user to that component and when he creates an issue ask him to fill in the component in the create screen and see if the issue is assigned to him. I have not checked it personally . But you can try
Note : I still think for the turnaround thing the user needs assignable permission .
Hello @ebrahim rezaian ,
That might be issue with permissions.
Please check if specified user has Assignable User permission and also check who is the Actor of the rule (the user, which performs the action), if it has Assign Issues permission.
@ebrahim rezaian as mentioned below, you have to have that specific group / project role of users in Assignable User permission. Logically the subtasks cannot be assigned to these users without that. The creation of subtasks is not related to Assignable User permission.