Error Adding a Release - Version Could not be committed

allanconybeare March 20, 2024

Hi, I'm getting an error when trying to add a release to a project - 

Version Could not be committed

A version with this name already exists in this project.

The version does not appear in the releases view 
https://xxxxxx.atlassian.net/jira/plans/50/scenarios/64/releases?vid=391 

But... when I'm in the project looking at an issue I can see and select the version in the FixVersion dropdown list. 
None of the issues with this fixVersion show up on my roadmap

Any help with getting this fixed will be greatly appreciated.

2 answers

1 accepted

0 votes
Answer accepted
allanconybeare March 20, 2024

Resolved - I manged to find it in the Project specific releases view which allowed me to rename the release. 

I then was able to commit a new release version, I then bulk updated all the issues with the old version number to the new fixVersion which fixed my problem. Finally I archived the now empty broken version. 

0 votes
C_ Derek Fields
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 20, 2024

Have you made sure that you are including Released and Archived versions when you view releases?

 

2024-03-20_15-43-13.png

allanconybeare March 20, 2024

Hi, thanks for your reply it was in unreleased. The view I was using where it wasn't showing was set to "All Statuses" so I don't think that this was the issue. Anyway I've managed to resolve it :) 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events