Some stories aren't presents in Sprint Start Event

[Benjamin]

Hi,

We've just noticed that our Burndown Chart report is incorrect.

Some issues aren't in the row of type "Sprint Start" even though they have been created and evaluated before sprint was started (no '*' beside these issues, we've also checked the story history: created, evaluated and affected to the sprint one day before it has been launched).

When these issues change to "done" state, a new row in the table has been added with:
- 0 story point in the "Increase" column
- event detail: "Issue completed"

There isn't any row of "Issue added to sprint" type regarding theses issues.

Then if we move theses issues to "In progress" state, a new row in the table has been added with:
- 'n' story points in the "Increase" column
- event detail: "Issue reopen"

When these issues change to "done" state, a new row in the table has been added with: 
- 'n' story point in the "Decrease" column
- event detail: "Issue completed"

We have compared issues with and without this problem but we can't find any common factor.

Any help would be greatly appreciated.

[Júnior Silva]

@Benjamin we have the same problem. Did you resolve it?

[Benjamin]

@Júnior Silva not really, support answer:

Thanks for confirming the result of the query.

From the query, it looks like you are using MySQL database. Since we do not have the logs from your JIRA, we were not able to identify the database that you are using.

Moving on to your issue, we understand your concern about the bug. The reason why the bug is currently not set to a higher priority is that we have less than 5 support ticket which is related to the https://jira.atlassian.com/browse/JSWSERVER-13996 bug. Part of the reason why the priority is not set to higher is also that there's a workaround to fix the report. Also, users also need to have a specific setup in order to be affected by this bug.

Most of the time, we try to focus on fixing the bug which affects the larger number of users and also more critical bugs. We do fix less severe bugs but it'll take sometime for less severe bugs to be included in our bugfix plan. We would recommend you to share your thoughts about the bug in the bug report that we have shared and add yourself as the watcher of the ticket so you'll be notified when there's an update to the bug. You may also get more information about out our bug fixing policy from the link below:

• https://confluence.atlassian.com/support/atlassian-bug-fixing-policy-201294573.html

Regarding your upcoming Sprint, can you discuss with your team if it's possible to rework your workflow (if you have such post-function) or update any external tool (using REST API) used to create the affected issue to prevent the issue to be auto-transitioned during creation? We understand that either one of the action will require additional work from your side but due to the bug and since we are unsure when the bug will be fixed, we would recommend for you to try updating the workflow or third party tool to avoid new issues from being affected by the https://jira.atlassian.com/browse/JSWSERVER-13996 bug. This way, there will not be any need for you to manually fix the affected historical entry.

Please let us know what you think for the workaround above.

Our workaround: delay the transition after creation about 5 seconds.

[Júnior Silva]

@Benjamin 

How did you implement the workaround (delay the transition after creation about 5 seconds)?

[Benjamin]

@Júnior Silva the problem was with issues created by an application using Jira REST API: when we created an issue and immediately send another request to ask a transition to another state thus the bug was present. Our workaround is to wait 5 secondes before sending second request.