Follow-up from "feat: adds sprint number to api and removes auto migration of meetings feature"
The following discussion from !37 (merged) should be addressed:
-
@Agrendalath started a discussion: This can be problematic -
get_sprints
retrieves all sprints related to the Jira board. Therefore, it returns something like this:[<JIRA Sprint: name='FAL.280 (2022-08-23)', id=693>, <JIRA Sprint: name='STAR.78 (2022-08-29)', id=705>, <JIRA Sprint: name='SE.280 (2022-08-23)', id=717>, <JIRA Sprint: name='BB.280 (2022-08-23)', id=720>]
STAR
sprints are shorter than others, so as soon as we have aSTAR
sprint with a lower ID than others, it can cause some unpredicted platform-wide behaviors - especially around theschedule_sprint_tasks_task
task.
Edited by Piotr Surowiec