Issues marked as Done still appears in a New Sprint

[Marco_Santiago]

We configured our workflow so that we have have a status of Deployed (for code that has been successfully tested and deployed). This status is mapped to a category of Done in the status definition screen. We also have status of a Closed in the workflow, for issues that are resolved for other than deployed status. This status is also mapped to a category of Done.

The problem that we're having is that when we set the status for an issue to Deployed, we're expecting these issues to drop off when we create a new sprint since these issues were resolved from the previews sprint. 

How do we get this to work?

[Martin Purkert]

Upgraded our test instance to current 5.2.7. Still the same problem.

[Ruchi Tandon]

Do you have JIRA Suite Utilities plugin installed on your site. The plugin has been known to cause problems like these if you have global transitions created using the plugin.

To confirm this, try to disable the plugin and then verify if you still have the problem.

[Sorin Sbarnea (Citrix)]

That's a JIRA bug, see vote https://jira.atlassian.com/browse/JRA-32132

[Andrey Mikuloff]

Also have same problem, but not on transition, it's raise on getIssueClient().getIssue(issueKey).get() - when try to get Issue with jira-rest-java-client-2.0.0-m2

[Sorin Sbarnea (Citrix)]

This is a documented bug, transitions are BROKEN on REST and this if more than 6 months old.

https://jira.atlassian.com/browse/JRA-32132

[Martin Purkert]

Any news on this issue? I have the same problem when trying to get issue data from an issue via REST API (Java Rest Client) that has global transactions. Currently we use Jira 5.2.1.

We also use JIRA Suite Utilities. But disabling the plug-in did not help to solve the problem.