Automatically assign issues to a release

[Anthony Pugliese]

I would like to have the ability to put prospective release items into a "holding bay" before marking them as Done.

why?  i would rather not mark anything as Done or completed until release actions are completed and
not everything that is ready to be released will go out in the next release. it may not make sense to do so and holding it back until there is a group of stories related

- If i had pre-created Release version, Can i drag and drop items to go into a "next release" column and they get added automatically to that unreleased version? waiting for confirmation that the release was successful and then the items can be marked as Done/Closed.

i can do all this manually, which is fine and doesnt create a lot of effort, but i would like to see if i can automate the bulk selection of items and assigning them to a release, but allow to go automatically be added once the items are manually moved to a status or column.

Essentially want the transition of the status to be the trigger for the item to be added to the next release and then to either manually or automatically trigger the version status to go from unreleased to released once a checklist or something has passed

[John Funk · Accepted solution]

Hi Anthony,

How will it know which release to attach it to? Assuming there is only one open release, take a look at this previous post for guidance:

https://community.atlassian.com/t5/Jira-Software-questions/Automatically-add-tickets-to-a-Release/qaq-p/1661598