Because of a simple user mistake the Version Report contains a very odd scope change.
User by mistake changed Story Points to issue ID - instead of a low 3 Story Points there were 547 Story Points saved. User immediately noticed the mistake and changed it to 3, but JIRA Agile remembers this and shows on the Version Report as a huge peak in scope change, which is irrelevant to the situation.
The goal is to remove this peak. How can this be accomplished?
Want to build your own Rovo Agent? Join this interactive workshop and dive into a powerful Rovo use case: improving resolution time with automated triage.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.