Some background: We have two boards, each based on a single procject, al la, 'project = Andy' and 'project = Bob'. At somepoint, it was pointed out that in Bob's velocity chart, some sprints from Andy's board was showing up.
What I'm seeing after some extensive filtering is that there is at least one issue from Bob that somehow ended up in an Andy sprint. That is, in a query for "sprint = 255" (where 255 is a sprint in the Andy project), I'm seeing a whole bunch of ANDY issues, and one, sole BOB issue.
My questions:
Thanks!
Community moderators have prevented the ability to post new answers.
Hello
Do you have news about this bug? We need edit/remove past sprints in Velocity chart.
Regards
We continue to see this happen today, it happened to multiple teams when another admin made workflow changes. orginally all 8 projects were using the same workflow, they updated one project to use a different workflow and that is when we began to see the boards cross poliinate amongst some transitions break.
Any suggestions on how we could have avoided this fiasco would be helpful, ultimately we spend a couple hours rebuilding all boards, updating the orginal workflows- transitions and validations to correct it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This happens when a ticket in one project that has already be scheduled into a sprint is then moved to another project. The sprint history stays with the ticket (even though it was associated with a different project) and I think this causes the sprint to be pulled into the velocity chart.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It appears, after some experimenting, that creating a new identical sprint board to the existing one (with the contaminating issues) clears up both the old and the now new board. We're no longer experiencing the problem, but the questions that still stands is "how'd the sprints get cross pollinated to begin with?"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.