I’m working with Jira and have set up two release versions: version 1.5 and the new release v2.0.
For version 1.5, I currently have 16 sprints configured, and now I need to establish additional sprints under version 2.0. I seem to be missing the correct procedure for adding these new sprints. Could someone explain how to properly configure and assign sprints to the new release? Any guidance on tweaking settings or correcting my approach would be appreciated.
hey, try updatin your board filter so new releases show. then you can add sprints directly in board settings. sometimes a quick refresh fixes it. hope it helps!
I encountered a similar issue when setting up releases in Jira. It turned out that the problem was not with the version setup itself but rather with the board filter restrictions. I refined the filter criteria to include the new release, and after refreshing the board configuration, the sprints became visible. It is also important to ensure that all settings, including permissions for managing sprints, are correctly configured. Revisiting these configurations helped me add new sprints to the additional release without further complications.
During my last Jira migration, I realized that new sprint setups might be impacted by how the board filter and permission settings are configured. I had a similar situation when expanding a release from v1.0 to v2.0. I found that manually editing the board filter to include the new release was necessary. I ensured the release version was explicitly allowed in the query. Also, when adjusting the board, double-checking the sprint settings often resolves visibility issues. This approach allowed the new sprint additions to correctly align with the intended release.
hey, try reindexing and check that your new version is linked in the board filter. sometimes a quick cache clear helps. i had a similar snag with v2.0 so relook over settings might fix it.