Sprint shows in two boards, unable to remove/hide it

[thalesc]

Hello,

I have seen multiple questions and even Atlassian KB articles about sprints showing in multiple boards. I understand the sprint is a separate entity and if your board filter allows it will show in multiple boards.

I have a slightly different scenario, and I am not being able to "remove" the sprint from the undesired board.

This is what happened:

• "Project A" with "Proj A Sprint 51" (correct project and sprint)
  • "Board A" Board filter: 
    

    project = "Project A" ORDER BY Rank ASC

• "Project F" with "Sprint 51"
  • "Board F" board filter:
    

    project = "Project F" ORDER BY Rank ASC

Some user from Project F selected "Project A Sprint 51" in the sprint dropdown of a Project F issue, since that moment the "Project A Sprint 51" started to show in the Board F, but after they changed the issue's sprint to the correct one, "Sprint 51", the wrong sprint "Proj A Sprint 51" remains in the Board F, showing 0 issues in the backlog or active sprints, if I search for it in the issue navigator/filter screen it also returns 0 results.

Looking at the AO_60DB71_SPRINT table, I see the column RAPID_VIEW_ID of the row of "Project A Sprint 51" is set to the "Board F" board id.

Has anyone had a similar issue like this? Is this a bug or desired behaviour?

Thanks

[Alexey Matveev]

Hello,

Try to update the original board of the sprint with this Rest Api method:

https://developer.atlassian.com/cloud/jira/software/rest/#api-rest-agile-1-0-sprint-sprintId-put

[Alexey Matveev]

Though I think it will not help. As long as history exists for this issue, you will see the sprint on both boards.

[thalesc]

Hi @Alexey Matveev thanks for your input. I think you were right in the second comment, the "problem" is the history of the ticket that was put in the wrong sprint.

I tried to run the API call to change the originBoardID

curl --request POST \
--url 'https://jira.mydomain.com/rest/agile/1.0/sprint/{26010}' \
--user 'user:pass' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{
"originBoardId": 4386
}'

The response was successful (200), but it returned the old originBoardId, so it looks like the API cannot change that parameter.

Since we have ScriptRunner I found a script that can delete the history of the issue, but I only found a code that delete the whole history

import com.atlassian.jira.issue.Issue;
import com.atlassian.jira.component.ComponentAccessor
def issueManager = ComponentAccessor.getIssueManager()
Issue issue = issueManager.getIssueObject("ABC-1234")
def changeHistoryManager = ComponentAccessor.getChangeHistoryManager()
changeHistoryManager.removeAllChangeItems(issue)

I am trying to find if there is a way to delete only a specific record (via the API) but it is not promising, I only found a way to do it by deleting the entry from the DB, but I don't want to go on that route because the impact is not that big.

Reproducing the issue on my test environment and running the code above makes the sprint go away from the undesired board. Without script runner you could also clone the ticket and delete the original since the cloning doesn't carry the history (apparently). So there are some alternatives.

Cheers,

Thales

[Alexey Matveev]

Thank you for your input!