We are able to sync all types of Jira tickets to Octane including sprint and release detils.
However the sprint is not set in Octane properly if a Jira ticket has a sprint history. Sprint history means that a ticket was in sprint A and was moved to sprint B after ending sprint A.
Then the ticket has a sprint value as "active sprint" and "completed sprint" as well. This confuses MFConnect and the incorrect sprint is synced to Octane or MFConnect does not identify a change on the sprint value and ignores the new sprint value.
Someone any ideas/experiences with that?
Thanks, Alex