Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2010

Jira Connector: Story's sprint is not assigned back to backlog in Jira Align

XMLWordPrintable

    • 4

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Closing a sprint in Jira will move the uncompleted story's to backlog or future sprints. If a story is moved back to backlog, this will not reflect in Jira Align when synced.

      Steps to Reproduce

      1. Create a Story in Jira Align or Jira and sync this.
      2. Create a Sprint in Jira and assign the story created in Step 1.
      3. Check the sprint state in Jira Align and make sure it's synchronized.
      4. Do not complete the Story, close the sprint in Jira and move this to backlog.

      Expected Results

      After it's synchronized, the story should also be in "unassigned" sprint in Jira Align.

      Actual Results

      Story still belongs to the closed sprint.

      Workaround

      Before closing the sprint in Jira, make sure to move the open Jira issues under the sprint manually to the backlog instead of using the option "Move to Backlog" when closing the sprint.

            [JIRAALIGN-2010] Jira Connector: Story's sprint is not assigned back to backlog in Jira Align

            Andrew Zhang made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Under Consideration [ 11774 ] New: Closed [ 6 ]

            Andrew Zhang added a comment -

            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

            Andrew Zhang added a comment - 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

            Victor Galli added a comment -

            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? 

            Victor Galli added a comment - 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? 

            Ronald Kager added a comment -

            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!

            Ronald Kager added a comment - 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!
            Alessandra Garcia made changes -
            Remote Link New: This issue links to "PS-174691 (Atlassian Support System)" [ 965772 ]
            Jennelle Stearns made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 954073 ]
            Jennelle Stearns made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 954073 ]
            CST JAC Workato Bot made changes -
            Labels Original: BW1 JiraConnector-other bulldog New: ACE-6270 BW1 JiraConnector-other bulldog
            Mario Sojo made changes -
            Remote Link New: This issue links to "ACE-6270 (Atlassian Support System)" [ 952946 ]
            Andrew Zhang made changes -
            Resolution Original: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Under Consideration [ 11774 ]

              2d32ad8bdc34 Andrew Zhang
              lsoronio@atlassian.com Leo Soronio
              Votes:
              42 Vote for this issue
              Watchers:
              48 Start watching this issue

                Created:
                Updated:
                Resolved: