Transition affected issues when releasing a version

Developing new software can be perfectly tracked within Jira. But at some point, new software has to be released and all related tickets should then be closed. To not doing this process manually, the following rule can be used to automatically transition all issues in the fixed version to be released to DONE.

Should I use an automation rule or workflow post function?

When to use this automation rule and when to use a workflow post function?

This use case is very useful, if there are several software projects with different workflows where all related issues have to be closed on releasing a new version. Configuring just one automation rule might then be the easier way to go. But if this scenario is only necessary for one workflow, the Transition Issues post function would make more sense. In this case you might want to check out our corresponding post function use case.

Project Event

Create a new rule and name it appropriately.

Providing a description will help you to identify what the rule does but this step is optional.

Add a Trigger → Project Event → Version Released

In this case, the Version Released event will be used. When no project is specified, the trigger will listen on every project for version releases.

Issue Version Selector

Add Selector → Issue Version Selector

Version Fields*

Choose Fix Version/s

Transition Issue

Next to Issue Version Selector click on Add → Action → Transition Issue

Mode*

Choose Transition to Status → Done

The target status has to be reachable from the current status, otherwise, the action will not be executed.

Error rendering macro 'excerpt-include'

No link could be created for 'DECADIS:Automation Use Case - Activate Rule Step'.

Screencast

This is how the configuration above should look on your screen

Related examples

Title		Automated action	Label	Parser functions	Style guide	Tech review	Workflow function
Inherit value from parent in Advanced Roadmaps hierarchy	Status	Update field action		fieldValue() first() parent()	TODO	TODO
Copy excerpted value from new comments	Status	Update field action		findPattern() first()	TODO	TODO
Add links to the issues in a ScriptRunner Issue Picker field	Status	Create issue link action Delete issue link action		issueKeysToIssueList() toString() toStringList() replaceAll() previousValue()	TODO	TODO
Bulk clear the issue resolution		Update field action	STAFF PICK		DONE	DONE
Add components of the epic to the current issue	Status	Update field action			TODO	TODO
Copy the parent issue comments to its sub-tasks	Status	Add comment action			TODO	TODO
Transition affected issues when releasing a version (manually)	Status	Transition issue action			DONE	DONE
Notify for high priority issue	Status	Send email action			DONE	DONE
Notify about date of last comment for high priority issues	Status	Send email action			DONE	TO DO
Send email when a field is updated	Status	Send email action			TODO	TODO
Notify the assignee one week before the due date	Status	Send email action			TODO	TODO
Sum up value in parent issue on field change in sub-tasks	Status	Update field action		fieldValue() sum() subtasks()	DONE	DONE
Close epic when stories are done	Status	Transition issue action		count() filterByStatus() issuesUnderEpic()	DONE	DONE
Automatically close parent when all sub-tasks are done	Status	Transition issue action	STAFF PICK	count() filterByStatus() siblingSubtasks()	DONE	DONE
Create issue link when issue is created	Status	Create issue link action		issuesFromJQL()	DONE	TO DO
Remind users to close inactive issues	Status	Add comment action	STAFF PICK		DONE	DONE
Add comment after seven days in the same status	Status	Add comment action			TODO	TODO
Delete the attachments of an issue 30 days after closing it	Status	Update field action			DONE	DONE
Add sub-tasks to an automatically created issue		Create issue action		getMatchingValue()			Create issue
Keep calculated custom field in sync	Status	Reindex issue action	STAFF PICK		NEEDS REVIEW	NEEDS REVIEW
Reindex issue on custom field update	Status	Reindex issue action			NEEDS REVIEW	NEEDS REVIEW
Reindex linked issues	Status	Reindex issue action			NEEDS REVIEW	NEEDS REVIEW
Scheduled project reindex	Status	Reindex issue action			NEEDS REVIEW	NEEDS REVIEW
Track issues mentioned in comments	Status	Create issue link action		findPattern() issueKeysToIssueList() toString()	DONE	DONE
Resolve issues when all options of a checklist are checked	Status	Transition issue action		numberOfAvailableItems() numberOfSelectedItems()	DONE	DONE
Create sub-tasks depending on selected values in a custom field	Status	Create issue action		toStringList()	DONE	DONE
Assign issues to your team during a transition	Status	Assign issue action		isInGroup()	DONE	DONE
Assign an issue to the last assignee on a transition	Status	Assign issue action			DONE	DONE
Re-assign issues and leave a comment	Status	Add comment action Assign issue action			DONE	DONE
Schedule issues for re-submission	Status	Transition issue action			DONE	DONE