Completing a sprint on the Agile board Sprint planning tab performs no actionIssue When attempting to complete a sprint via Agile Board > Sprint Planning, selecting Complete Sprint performs no action and the sprint does not complete. This issue affects the Agile Board, Sprint Planning, and sprint completion workflow, and may be caused by emoji or special characters in sprint records, or by Dictionary Entry Overrides on state fields that conflict with out-of-box sprint completion logic. ReleaseParis+CauseSpecial characters and emojis in sprint records prevent Agile Board actions from functioning. If emojis are present in columns such as Short Description, the Complete Sprint action fails. Examples of problematic characters: ⚠️, 📋, 🎯 This issue can also be caused by a customization or Dictionary Entry Override on the state field of the rm_sprint, rm_story, or rm_release table that conflicts with the out-of-box sprint completion logic. A non-out-of-box read-only override on the state field silently prevents the sprint completion workflow from executing. Additionally, having more than one sprint in Current state for the same Agile group can prevent completion, as Agile 2.0 (Kingston onwards) permits only one current sprint per group.ResolutionIdentify the sprint associated with the Agile board where the Complete Sprint action fails.Navigate to the sprint's related story or task records and open each Short Description field.Locate and remove any emoji or special characters (for example: ⚠️, 📋, 🎯) from all Short Description fields in the sprint.Save the updated records.Return to Agile Board > Sprint Planning and select Complete Sprint to confirm the action now completes successfully. If removing emojis does not resolve the issue, verify that no non-out-of-box read-only Dictionary Entry Override exists on the state field of the rm_release, rm_sprint, or rm_story table. Revert any such overrides to the out-of-box configuration. Also confirm that no more than one sprint is in Current state for the affected Agile group.