I would like to automatically assign sub-task to a developer who created it.
I've already tried using post function, but since there is no specific creation event for sub-tasks it works also for other issue types.
I am currently experimenting with automation feature but I am not really familiar with it and I am running out of ideas.
I tried using trigger "issue created" but it doesn't seem to catch those subtasks no matter what condition I am using.
i just wanted to add that you can create a sub-task specific workflow if you wanted to leverage PF. But it may be that automation is the better/simplier approach and will defer to John to work that to closure with you here.
It works for all users , who creating sub tasks.
created an automated rule , works perfect for me. check the below
If it works, please accept my answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your message, unfortunately I have already tried the PS solution you proposed and it affects not only the sub-tasks but other issue types as well so it is not exactly what I am looking for.
I replicated the automation you posted and it is not working for me. It is not recording any logs. My team likes to use this view to add new sub-tasks, do the way how the issue is created affects the automation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe try creating an additional transition to Done for Sub-tasks and add a Condition to the transition for Issue Type = Sub-task. And then place the Deep Clone post function there.
Then update the existing transition to Done to add a condition for Issue Type != Sub-task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would creating a transition to Done help here? I want to assign the sub-task to the user who has created the ticket because devs in my team like to create sub-tasks for themselves during meetings.
It happens before transitions to Done.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kryzysztof,
Can you share the Automation rule that you have created so far? And also what it is not doing that you would like for it to do?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried something like that but it is not being executed. Tried to replace the condition with "Related issues condition" but with no success
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.