Hi folks,

We're updating the Connector logic to address this suggestion, which is rolling out with 11.9.

Note that our fix will cover the case outlined in the Steps to Reproduce above (Jira Sprint is closed, but Jira story is not yet Completed -> results in Jira Align story now having Sprint value: Unassigned). Out of scope is addressing situations where the story is marked as Completed in Jira. The reason that is out of scope is that there’s additional complexity and uncertainty to addressing that case, and we don't have the information available to confidently know that a story should be in the Unassigned backlog in Jira Align.

We're releasing this logic change alongside a few guardrails, to ensure that customers don't inadvertently delete sprint values in Jira. You can read more about that here. 

Thanks,

Andrew Zhang

Hey 8b6936ac7b37: I think we're going to see some movement on this in 11.9.0/11.9.1, which is scheduled to hit your JA Cloud Production environment during this weekend's release of 11.9.1 (for anyone whose JA Cloud Production environment is still on the default bundled release track). Not sure if you were aware of that, but it looks like you picked the perfect time to comment on this ticket You can read more about the broader challenges related to this issue in [this announcement that's dedicated to this topic|https://help.jiraalign.com/hc/en-us/articles/34627859776404-Upcoming-reintroduction-of-Jira-connector-sprint-assignment-logic.]

I also recommend reading through the Release Notes for 11.9.X and scrolling down to the section titled: "Reintroduction of Jira connector sprint sync logic"

Hey 2d32ad8bdc34 & lsoronio@atlassian.com, since the article i've linked above has made it clear in the opening paragraph that both JIRAALIGN-2010 and JIRAALIGN-4006 are targeted to have been addressed in 11.9, would you be willing to update the status and fix version fields on these two issues accordingly? 

What will be next?  

This bugticket has still 42 votes and this bug is now 4.5yrs old 

.. it is still a really annoying bug we constantly trap into - especially during PI plannings.

please proceed!

Hi folks, we were planning to roll this out with the 11.3.x release, but we ran into an unexpected bug. As a result, we have rolled back the changes. More details here. 

We are going to re-assess how we can ship this back out to customers. For now, the behavior remains the same as before, a story's sprint is not assigned back to backlog in Jira Align.

I'll provide updates on this ticket when I have updates to share.

Andrew Zhang,

Product Manager, Jira Align Connector 

What release will this be in?

Hey folks,

I'm the Product Manager for the Jira Connector. We investigated the issue, have a solution in mind, and think we can address the suggestion by the end of June 2024. As such, I've updated the status of this ticket to Under Consideration. I can update it to In Progress, once we start working on the ticket, or if we run into any roadblocks. 

Note that our fix will cover the case outlined in the Steps to Reproduce above (JSW Sprint is closed but story is not yet Completed). Out of scope is addressing situations where the story is marked as Completed in JSW. The reason is that there’s additional complexity and uncertainty to addressing that case, and we don't have the information available to confidently know that a story should be in the Unassigned backlog in Jira Align. But we believe that the fix we're introducing will help solve a majority of the issues arising today.

We just went through 10s of hours of cleanup in the work tree at the end of our first program increment using Jira Align. Moving forward, we will manually move stories and tasks to the backlog or a future sprint BEFORE we end the sprint in JS, but agree this is a BUG - notably, neither of the solution architects assigned to us by Atlassian as part of the integration support package in our enterprise contract mentioned that we need to follow this procedure at the end of sprints. 

any update on this issue? Not being able to use Jira's Move issues to Backlog button (i.e. manually having to move issues to backlog) causes confusion and is very inefficient for users. Please remedy as quickly as possible.

Atlassian Team, 

We need this issue fixed ASAP, Although Jira Retains the History for people to view the historical data for the Sprints a Story/Feature worked in. 

Jira Align is not behaving as Expected, Instead of a Improvement this need to be prioritized as a Bug. 

Jira Align does not synchronize Sprint field in Jira to Iteration in Jira Align. This is a Bug

Hi Kyle ,

we need your attention here because of the significant planing issues due to the wrong place of these stories.

I know, Jira Software explicitly keep these stories in Backlog even that have some Sprint values. Technically you need to just keep in touch Jira Software Product Development Teams and reflect this mechanism to Jira  Connector in Jira Align.

Looking forward to hearing good news

Ahmet Kilic

Enterprise Agility Consultant