Community Announcements have moved! To stay up to date, please join the new Community Announcements group today. Learn more
×Hello! Below is a solution that I have tried. I have tried the original solution and the "it worked" suggestion, and I am still unable to assign an issue to a specific sprint. Do you have any additional suggestions to get this to work? I have tried both name and Sprint ID.
Hello, @Susan Cain !
Could you share with us a screenshot of your automation rule, the value you're using in the Sprint field, and any errors or unexpected behavior you're seeing.
This will help us better understand why the suggested solutions didn't work for you.
Rule is set up:
Work Item is created, assigned to 2025.Q3.5 FS when I put the smart value as: {{sprint.name.match("New Stories Added - FINS").id}}
I updated the rule and it put the new work item into backlog
updated rule again to be {{sprint.("New Stories Added - FINS")}} - added work item, assigned to backlog
It has to be something stupid simple that I am missing. I appreciate your advise!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Susan Cain
Adding to the suggestions from @Izabela França ...
I note a few things with your rule that need adjustment. But first:
What problem are you trying to solve? That is, "why do this?" Knowing that will help the community provide better suggestions. What you seem to be trying is:
GIVEN a future sprint exists named "New Stories Added - FINS"
WHEN a work item is created
AND that work item's type is "Report Enhancement..."
THEN add that work item to the future sprint named "New Stories Added - FINS"
Until we know your scenario...
The Work Item Created trigger has a known racetrack timing problem. This means the rule can start before all of the data is available, potentially leading to weird rule symptoms and errors. Atlassian knows about this problem, and is making architectural changes to address it. However, there is known timeframe for the fix.
And so my recommendations are:
Next, the smart value expression shown in the article you linked to cannot work as you expect. The reasons for the rule you show are:
Putting all that together, and if the scenario is as I described, your rule will need to either hardcode the id for that specific sprint, or use the REST API to find the sprint to add it.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Susan Cain,
Here are a few troubleshooting steps for sprint assignment automation:
Common Smart Values for Sprints:
{{sprint.name}}
- for sprint name{{sprint.id}}
- for sprint ID{{issue.sprint.name}}
- current issue's sprint nameThings to Check:
"{{sprint.name}}"
or use the exact sprint ID as a numberAlternative Approach: Try using the "Sprint" field with a static value first (just type the sprint name directly) to test if the automation works, then switch back to smart values.
Debug Tip: Add a "Log Action" before the sprint assignment to see what value {{sprint.name}}
is actually returning.
Could you share a screenshot of your automation rule setup? That would help pinpoint the exact issue.
Feel free to DM me if you need more detailed troubleshooting help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.