On this page
Use case
In Jira issues can be categorized not only by issue type or project, but also by components. They can be widely used and offer useful additional information for issues. But it is also possible to merge existing components. By default, you won't notice such changes. That's 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!
Enable the rule by clicking on the Enable button →
Screencast
No screencast available at the moment.
Related use cases
If you still have questions, feel free to refer to our support team.