Jira Sprint Changelogs aren't registering in some cases

[McKenna Hogan]

Hello, 

My team utilizes the history of each issue in the form of changelogs. We pull Jira Data from an API to see this history of each issue. I have noticed that the sprint changelog isn't working when we create an issue using the "create" button. When someone uses the "create" button, the changelog "none -> sprint x" wont' appear. It still won't appear even when the person manually assigns the sprint when using the "create" button.

The "none->sprint " changelog will only register when we create a task from the backlog view using "+create issue" or in the board view using "+create issue" under any of the statuses. Even though the person isn't manually assigning the sprint here, the changelog "none-> sprint x" will shows up in these cases.

This leads me to believe it is a problem with the "create" button, or possibly how we have the create button set up, since the problem occurs even when the person manually assigns the sprint from using the "create" button. But the problem doesn't happen when the sprint is automatically assigned when using the "+create issue" buttons, or the person manually assigns the sprint when using the "+create issue" button. 

Here is 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

Using the "create" button has been the only way we have been able to reproduce this problem.

[Bill Sheboy · Accepted solution]

Hi @McKenna Hogan 

This appears to be a design choice by the team-managed project (TMP) people.  Specifically for these scenarios:

GIVEN there is an active sprint in a team-managed project
WHEN a story is created with the top-navigation Create button
AND the sprint is selected when the issue is created
THEN the sprint is set at the same time as creation
AND there is no separate history entry for setting the sprint

GIVEN there is an active sprint in a team-managed project
WHEN a story is created with the on-Scrum-board Create Issue button
THEN the story is created first
AND the sprint is set afterwards
AND there is a separate history entry for setting the sprint

There are other two-step implementations like this in Jira Cloud, such as with issue linking.

I did not find any open suggestions to modify this behavior, so please add one or work with your Jira Site Admin contact the support team to learn more: https://support.atlassian.com/contact/#/

Kind regards,
Bill

[McKenna Hogan]

Thank you for answering. This is very helpful - thank you!