When a bug ticket in Jira is closed, the associated sprint field is automatically changing to "None".
I've encountered an issue where, after closing a bug ticket, the Sprint field on the ticket is set to "None." The sprint associated with this ticket was not active at the time of closing.
Is it expected behavior for the Sprint field to be cleared when a ticket is closed if the sprint is not active? Or could this be a result of a configuration issue or workflow rule that I'm not aware of?
Any insights or suggestions on how to prevent this from happening would be greatly appreciated.
Hi @이기쁨
The behavior you're experiencing, where the Sprint field is set to "None" after closing a bug ticket when the sprint is not active, is not typical default behavior in most issue tracking systems like Jira. Here’s an analysis of what might be happening and how to address it:
Workflow Post-Function or Automation Rule:
Sprint Closure Behavior:
Custom Script or Add-on:
Check Workflow Configuration:
Review Automation Rules:
Audit Log or Change History:
Test in a Sandbox or Staging Environment:
Review Sprint Closure Process:
Hi @이기쁨 ,
Welcome to the Atlassian Community!
The field value could be cleared for many reasons.
1- An automation rule can clear the field value to check if any automation is triggering when the issue is closed. (You can close the ticket and check the audit logs under global automation)
2- Please check the workflow post function on the closed transition, there could be a post function applied to clear the field value.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.