Why is it possible to add content to the released version?

[Inna S]

Hi, 

we ship versions and once the version is marked as 'released', its content in terms of associated stories and defects cannot be changed. 

But Jira let me freely add a new story to the version marked as released. 

Two questions:

1. how does this make any sense?

2. how to lock the version content when its status is set to 'released'?

Thank you,

Inna

[Nic Brough -Adaptavist-]

And when someone raises an issue that you discover that you've already fixed in a released version?  You don't want to tell them where it was fixed?

[Inna S]

There is a way to do this: today we can close this second report as a duplicate. That is one of the 'resolution' options.

The content of the shipping container really should not be changed past the point of the custom check, right? So why the software can be any different?

[Nic Brough -Adaptavist-]

That's not the right way to do it, because you're not telling the person who raised it what version it was fixed in. (As well as closing their report as a duplicate)

The analogy with a shipping container going through a customs check is wrong.

A better one would be that a customer asks if you have something and you are telling them that "yes we do, it's in that container over there"

[Fabio Racobaldo _Catworkx_]

Hi @Inna S ,

released versions should be make still available just for Affect Version field and not for Fix Version. It doesn't make sense as you correctly said.

There is an open request for that on the Atlassian backlog https://jira.atlassian.com/browse/JRACLOUD-5830

Fabio

[Inna S]

Thank you, @Fabio Racobaldo _Catworkx_ , this request is from 2005. And it has related requests from 2003. I get at this point it is safe to assume they are not going to do anything about it.

How do you please live with this?

[Fabio Racobaldo _Catworkx_]

you can add some validator on transition that validates fix version is not released but on edit you can't :(