I cannot assign tickets to a Release

[Samuel Justus]

I created a release, but I cannot figure out how to assign tickets to it. There is no field within the ticket details in which I can add the release, and I've tried every option via "configure"

I would think that this...

Would correspond to this...

But apparently it does not because my Release is nowhere to be found 

[KAGITHALA BABU ANVESH]

I think releases are created over project level. May be it's not possible .

[KAGITHALA BABU ANVESH]

Hi @Samuel Justus 

I think the fix version field is not editable / not on create screen.

Can you please recheck the field is available on all screens in project.

[KAGITHALA BABU ANVESH]

And also please check ,

Do you have resolve issue permission in project settings. 

Check this once also

[Jack Brickey]

yes - you need resolved issue permission to set the Fix version field.

[Samuel Justus]

@Jack Brickey @Kagithala Babu Anvesh 

I have the permission. When I click on the fix version field I search for the Release I created and it does not show up. I get "no results"

[KAGITHALA BABU ANVESH]

HI @Samuel Justus ,

Can you create a ticket in Incognito window once.

while creating , please check are you able to select "Fix Version" or not.

I just created a new project with default template in Cloud. Created a version. I'm able to choose my fix version.

I think there is no issues from Atlassian end. Please try in incognito window and check once.

[Samuel Justus]

It worked and I think I realized the issue. I created the release in the wider team project, that pulls in various specific projects, of which the release may encompass.  Do you know which filter/schema I need to update for the release to allow tickets from various projects? 

For reference, Team Project A contains tickets from Product Projects X, Y, and Z. I want add tickets from X, Y and Z to the release for Project A

[Jack Brickey]

not following here. how are you pulling in issues from multiple projects into another project? Maybe you mean you have a board that encompasses issues from multiple projects? Releases belong to a single project. I'm sort of lost at the moment.

[Samuel Justus]

@Jack Brickey  We have the project "Team A" which has our sprint board, which includes tickets from various projects that Team A is working on

We have also have another project which has tickets from other projects in the backlog as well, which confused me a lot when I first joined this team I'm on now :)

Below is a screenshot of the project where I want the release to live. I can't attach tickets from AT and ATR to a release within Striker?

[Jack Brickey]

ok so the issue here (i think) is that you are trying to assign "Team A" releases to issues in other projects. As I said releases can't be shared across projects. For example if you add release version 1.1 in project "Fred" and go to project "Sally" and look at releases there, if that project has 1.1 it is NOT the same as the 1.1 in Fred. 

If i'm off track here please excuse my tangent.