Sprint changelogs aren't registering

[McKenna Hogan]

Hello,

My team has been problems with assigned sprints not showing in the activity history. Normally, when a task is created and assigned to a sprint, there is a history log saying "none -> Sprint x". However, this was not the case with this task. Even though my Sprint value on the right showed Sprint 15, there was no evidence of this in the history.

There was no history log of being assigned to Sprint 15 until I deleted Sprint 15 from the Sprint option, then reassigned it - as you can see in this screenshot

Has anyone else had this problem? Does it have to do with making the task using the create button in the board view instead of the "+create issue" option in the status's themselves? It is creating problems for us when we pull the changelogs via the Jira API.

[Lígia Zanchet]

Hello McKenna

Thank you for reaching out to our community with this question!

When you create an issue directly from a sprint, the Sprint field is automatically filled in during the creation process. Because of this, the history won’t show a change from "none" to "sprint 16" as it would if you updated the Sprint field after the issue was already created.

Hope that helps 

[McKenna Hogan]

Hi - thanks for commenting!

I thought of this. But when I create an issue from the "+create issue" selection under each status in my sprint board, it is also automatically filled in. But it still shows a change in the history in this case.

Then, when someone on my team uses the "create" button, and manually fills in the sprint themselves, it doesn't register under the history.

So the sprint being assigned manually only shows in the history if I did not use the "create" button. And will still show under history even if it is automatically assigned ( as long as its not from the "create" button)

See my comments on the post below to see examples of this. I was able to recreate the problem and posted screenshots of each :) 

[Lígia Zanchet]

Hello McKenna,

Thank you for your patience and for providing such a detailed explanation of the issues.

After discussing this internally, we found the following reason for what you're experiencing:

When we use the "Create" button at the top during issue creation, the sprint is assigned at that time. Unfortunately, this action doesn't leave a trace in the audit log.

However, if you use the "+ Create" button directly from the sprint board, the issue is created and the sprint is automatically populated afterward. This action does leave a trace in the audit log, which explains the difference.

Please let me know if you have any further questions or need additional clarification.

Best regards 

[Benjamin]

HI,

I didn't see this issue. I created an issue on the board and add it to the sprint and observe it update the activity log. Wondering if this could be a bug.

Is this specific to this one task? or are you able to recreated this with any task you create going forward?

[McKenna Hogan]

Hi - thanks for commenting

I will try to recreate this issue and get back to you

[McKenna Hogan]

Hello - I have a recreation of this bug.

The first screenshot of DART-698 shows that under history, when the task was created then assigned to Sprint 16, there is a changelog showing "none -> sprint 16". This task was created in the epic view. Then the user created the task by using the "+ child" icon. The sprint was a manual assignment by the user.

This second screenshot of DART-699 shows that under history, there is no changelog for "none-> sprint 16" even though under details, you can see that it is under sprint 16. The user created this issue by using the "create" button in the board view of our sprint. then manually assigned the sprint.

This third screenshot is of DART-700 shows that under history, there is a changelog of "none->sprint 16". This task was created using the "+issue" option under the "in progress" status of our sprint board. Sprint 16 was automatically assigned by Jira

This makes me think that it is a problem with the "create" button in the board view of our Sprint. Since it is the only way in which we create a task that produces this error.