Sprint field are auto populated to the recent one.

[Nicolai Viținschii]

Hey everyone,

I'm using Great Gadget Add-on, and I noticed inconsistency when I create sprint burndown gadget compared to built-in functionality. Short investigation showed that the problem is with the tickets with the status [Discarded], for some reason the field [Sprint] is automatically updated (by the PO) and new sprint is added. I checked the Automation - and it is not the case. Anyone have any idea why it is happening? The issue is not in Great Gadget Add-on, since the auto-population started before we installed add-on.

Thanks in advance for your help

[Bill Sheboy]

Hi @Nicolai Viținschii 

I recommend starting with an example issue and reviewing the history to learn when / how / who is adding the sprint.  That may clarify the cause, such as comparing that to any automation rules running at the same time.

Until that is checked, I wonder...

• You describe a status "Discarded"
• For Jira Scrum boards, issues are not consider complete until they reach the right-most column of the board
• And so if the "Discarded" status is not mapped to the right-most column and someone completes the sprint, the issues will be added to the next sprint (or the backlog)

Do you think this may be the cause?

Kind regards,
Bill