You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
My team is working on some stories that are to be deployed in November with version 23.11. The stories are being worked on this April with version 23.4 and are tagged to this 23.4 version. what are the possible issues this might cause.
Hi @udensia Manga welcome to the community. If these issues that are tagged with 23.4 and are released prior to 23.11 then they'll be marked as Released in Jira's release hub. Further to that any reference to the release 23.4 will have the tickets in it but 23.11 will not. So again in the Release Hub you will not see those issue if you are in 23.11. You can tag issues with more than one fixVersion but I don't know if that will remove the confusion this might cause. If these tickets are being released in 23.11 and you know this why would you want to apply the version of 23.4?
Thanks @Craig Nodwell I usually track the Capacity per release so since these stories are being worked on during sprints in 23.4 so they are tagged to that release.
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.