If any issue is move from backlog to active sprint it should be automatically assigned to user.
Hey Fahad,
Can you please explain who should be the assignee in these cases? Is it suppose to be the person who added the issue to the sprint?
Hi @Sagi Gueta
Adjust the workflows related to the issue types used in the project.
Add a post function when is changes to a certain status the assignee is sst based on the actor of executing the transition.
This wil only work if issues that are added to a sprint also change status.
It has it's caviats, jusr as the automation @Ste Wright proposed.
Hey @Fahad Mubarik ,
I've revisited your requirements, and I've created this automation.
The automation will affect only created issues that were added to an active (open) sprint. If you create an issue and associate it to an unactive sprint, then it won't triggered.
Hope you'll find it usefull
Hi @Fahad Mubarik
Can you clarify the logic for this?
For example, is it the user who moves an issue from the Backlog to a Sprint should be assigned the issue?
---
If yes, this might work (although it's not foolproof):
The rule checks if the issue is in an active Sprint, and if it is in at least one, it assigns to the user.
But the reason it's not foolproof is it's not checking the exact Sprint added, it's just looking for any Sprint which is active.
Ste
No it is not the person who added the issue,i just want if any issue move from backlog to active sprint then it should be assign to "Fahad" like this
Great Thanks
@Sagi Gueta i have make it more simple and it works
Looks good!
If you have a standard subscription in Jira (not premium), and you are running a big team, I'd suggest add a post-function within the workflow instead using Jira Automation.
Atlassian changed their automation counting system so each account has 1000 success automation limit per month (the usage is presented in automation section).
It looks like you're new here. Sign in or register to get started.
