Creating partial releases in JIRA without affecting completed tasks

[SparklingGem]

I need help with JIRA release management and would appreciate some guidance.

Currently I have multiple completed features sitting in my “done” column. My plan is to eventually bundle most of these features into a major release called v2.0.

However, there’s one specific small feature among the completed ones that I want to ship earlier as version 1.21.

Is there a way to create this partial release (v1.21) with just that one feature without having to move all the other completed features back to “ready for testing” status? I’m trying to avoid unnecessarily notifying the whole development team about status changes for features that are already finished.

Any suggestions on the best approach for this scenario would be really helpful.

[amelial]

just clone the ticket and assign it to version 1.21. leave the original in done for v2.0. yeah, it’s some duplication, but you won’t mess up the workflow or spam the team with notifications. we do this constantly when product cherry-picks features for different releases.

[charlottew]

Create a release branch or use labels to isolate your feature without messing up the board. I hit this same issue last year - needed to hotfix one component while keeping everything else staged for quarterly release. Tagged that specific ticket with ‘hotfix-1.21’ and filtered release notes based on the label instead of column position. Most CI/CD tools can grab JIRA labels for automated deployments. Your done column stays clean and won’t trigger workflow notifications since you’re not moving tickets around. Other completed features sit there until you’re ready for full v2.0 rollout.

[Hazel_27Yoga]

You’re using board columns for release management when you should be using JIRA’s Fix Version field instead. Don’t move tasks around columns - just edit the feature you want to release early and set its Fix Version to 1.21. Leave the others unassigned or set them to v2.0. When you’re ready to ship, mark version 1.21 as released in your project settings. This keeps your board clean and won’t spam anyone with notifications since you’re just updating metadata, not changing workflow status. I’ve done releases this way for years - way cleaner than trying to manage them through kanban columns.