-
Suggestion
-
Resolution: Duplicate
Issue : Ability to Use Component leader in Jira Automation
Problem Summary:
- Presently, if the user has the requirement in the Jira Automation rule that whenever a Component is being changed for an issue, the assignee changes to the Component Leader.
- The component field can be edited or used as below
Case 1:
Make the component field mandatory in the project.
Say the project has 2 components and a default assignee for those components is the component leader.
While creating the issue, if the user selects any one of the components, the default assignee would be the component leader.
Case 2:
This could help via automation.
We can create a rule as below
1. Trigger: when field value changes
2. Issue fields condition > Components > Equals> ( enter component name example hello ) > Assign issue > enter the email address of component leader for hello>
3. Issue fields condition > Components > Equals> ( enter component name example Test component ) > Assign issue > enter the email address of component leader for test component>
- This method will only help if the components are less in the projects rather 2 or 3.
Suggestion:
It would be great if automation was a feature to assign issues directly to the component leader when the component field is updated.
Something like
When the issue field is updated> Component ( to a certain component) > assign issues to the component leader.
This will help me the project contains many components and will prevent manual intervention
- blocks
-
AUTO-485 Automation support for working with components and component leads - new triggers, actions and smart values
- Gathering Interest