Here’s a summary of the situation:
Also, Im not sure what are the sprints that are showing on that dropdown.
Hi @Francisco,
Welcome to Atlassian Community!
The values that you see when setting the sprint on an issue is not tied to the project the issue lives in, this is so that you can have issues in different projects being added to the same sprint. And this is why in the automation when you are trying to set the sprint you will see Active sprint (xxx) and Next sprint(xxx).
In order to set the exact sprint that you see on the board in your first screenshot you need to know the sprint Id, similar to what I do in this automation that creates recurring tasks when we create a new sprint
In your case since the sprints already exists you can either have a component that creates the smart value and sets it to the corresponding sprint Id based on the dates, and then use that smart value to set the Sprint field like I do above. The other option would be to use the REST API to get the next sprints, and then set the smart value to the corresponding sprint based on the date. This would be a bit more complex, but you would not have to go in and modify the automation every time you create a new sprint like you would have to do if you do option one.
Great! Thanks a lot! For now I've hardcoded the sprint id. Later I can work on a more automated solution. Screenshot attached. Thanks a lot!
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.
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.