You can have a workflow post function to automatically assign the ticket to the component lead, when a component is selected during issue creation. Is that what you meant?
Not sure what you meant by choosing a component lead when creating the issue because you can't change component lead while creating issues. Are you talking about a custom field instead?
Great answers! Another request is when cloning an issue that is assigned to the component lead and then 'edited' for new fields, for the new component lead to also be the new issue assignee.
Meaning, I created an issue and based on the component, the same user is the assignee. Now when I clone this same issue and edit the fields (component being one of them) the new component field option assignee should also now be the issue assignee.
Currently, it's not changing the 'assignee' when editing the component field.
Once assigned, JIRA won't change the assignee based on changes in the component, unless you explicitly do that in a workflow action. In the case of cloning, the assignee will not be modified unless the assignee is not valid in the target project of the cloned issue. Hope that makes sense.
You can do this off-the-shelf. Look at the list of components, and you'll find some settings to the right about who the default assignee is - project lead, unassigned, project default or component lead. No need for post-functions.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs