On this page
Use case
When a component is deleted in Jira you can "merge" it with an existing component. By default, you will not notice such a change. This is why the following automation rule will take care of these merges.
As soon as a component from the current issue has been merged, the assignee will be notified about this change in a new comment.
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 → Component merged
In this case, the Component merged event will be used. When no project is specified, the trigger will listen on every project for component merges.
Issue Component Selector
Add Selector → Issue Component Selector
Add comment action
Next to the Issue Component Selector click on Add → Action → Add Comment
Comment's text*
Hi [~%{selector.issue.assignee}],
the component *%{trigger.component.name}* has been merged. You may want to take a look at this merge.
Cheers!
"[~" is the notation for mentioning users by their username.
"*" is the notation for making text bold.
Enable the rule by clicking on the Enable button 
→ 
Screencast
Related use cases
| Title | Automated action | Use case description | Complexity |
|---|---|---|---|
| Notify assignees when components are merged | Add a comment to an issue as soon as one of the selected component has been merged. | BEGINNER | |
| Remind users to close inactive issues | Periodically add a comment mentioning the assignee to all unresolved issue that haven't been updated for more than 30 days. | BEGINNER | |
| Notify the project lead on priority changes | When the priority is changed to "Blocker", a comment will be added with a user mention alerting the project lead. | BEGINNER | |
| Re-assign issues and leave a comment | Assign all issues from a user on vacation to another user and add a comment to inform the team. | BEGINNER |
If you still have questions, feel free to refer to our support team.
