Just upgraded from 8.9.1 to 8.12.3 and we have reports that a project's sprints are not visible to select or manually typed in anymore in the Jira sprint field in an issue. Was there something in between the versions that could have caused this? Not sure where to start to look...
We're experiencing the same thing on 8.12.2. We're testing out a potential workaround: try viewing the backlog section of the associated board and then go back and edit an issue. Viewing the list of sprints from the backlog page seems to allow the field to populate again.
I followed up with a support ticket to Atlassian. This is the response I received (copied below). Appears this issue is corrected in version 8.14.0. .. .or if you're utilizing Jira Cloud.
++++++++++++++++++++++++++++++
After reviewing the context and performing tests in one of our local instances, we could confirm that it was the same situation as described by the community and that this behavior is still present on the 8.13.0 version.
Based on this, the answer to your questions is below:
Has this issue been resolved by Atlassian yet?
This issue was fixed on the 8.14.0 version.
Is it also happening to those that have migrated already to Jira Cloud? We'll be migrating to the Jira cloud by end of this year and perhaps that environment won't have this issue?
Regarding Jira Cloud, its versioning is different from our Server/Data Center applications. Cloud environments are constantly updated by Atlassian as we manage their infrastructure. Additionally, after researching this topic, and considering that it has already been addressed in Server/Data Center, we did not find any evidence that this behavior affects Cloud instances.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't have an answer/resolution but wanted to mention that this issue doesn't appear to be corrected in version 8.13.0 (my company upgraded last Fall 2020) and are experiencing this issue too!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same issue in 8.12.1
However, the workaround above from IT Team helped -- viewing the backlog section of the associated board, refreshing the ticket and then editing the sprint field populated the sprint options successfully.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian has said this issue is corrected in version 8.14.0 and does not appear in Jira Cloud. Just FYI. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi. We observe a similar problem after upgrading to version 8.12.3
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian has said this issue is corrected in version 8.14.0 and does not appear in Jira Cloud. Just FYI. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.