Set Component Lead automatically in issues based on added component

[Sandra.Abi-Khalil]

I'm trying to use the field Component Lead to benefit our situation, as a team supporting a large number of applications with different system owners. Each application has its own Component set up and there it's possible to define a Component Lead for the Component.

I would like for the Component Lead to be updated automatically in any issue where a particular Component (with a defined Component Lead) has been added, but this doesn't seem to work that way, or am I missing something? Do I need to try to set this up myself though a Jira Automation rule?

[Walter Buggenhout]

Hi @Sandra.Abi-Khalil,

The component can be set automatically when an issue is created. The requirements for that to work is that you set the default assignee in your project settings to component lead and that a component is added while the issue is being created.

If you want to assign existing issues when a component is added later on, you would indeed have to rely on (some sort of) automation to make this happen.

Hope this helps! 

[Walter Buggenhout]

Given your latest post here:

I want to populate the field Component Lead with the registered Component Lead in the Component, when there is a Component in an issue.

Our Component Leads aren't going to be assigned the work, they are our contacts for questions regarding the respective applications.

you'll definitely need to automate setting the field. Unfortunately, retrieving the component lead via a smart value is not supported yet and part of this feature request: AUTO-485. As a workaround, you may want to look at this related thread.  

[Sandra.Abi-Khalil]

Hi Walter,

I'm not sure if we're talking about the same thing - I'll try to explain myself better.

Let's say one of the applications we support is Paypal and we have a business system owner for that application whose name is Betty.

When I set up the Component "Paypal" in our Jira I have added "Betty" as the Component Lead. Now, whenever a ticket has the Component "Paypal" I want the field Component Lead for that ticket to be populated with the person "Betty". Betty should not be the assignee for the ticket however, since she's not the one actually doing the work to solve the issue - that's done by one or several of the devs on my team, not by Betty, who is the one we might need to contact for input on requirements or user acceptance testing etc.

The reason we would benefit from this is because we support around 100 applications and no one can keep track of all the business system owners and I would prefer to not have the developers having to look for that information outside of jira.

[Sandra.Abi-Khalil]

Ops, page got updated when I posted my response and I saw that you had already updated your response :D Thank you!

[Walter Buggenhout]

@Sandra.Abi-Khalil , once more tapping into your last comment:

It would be far easier if it were possible to go:
If Components is not empty -> Edit issue field [Component Lead] to [Copy from Component in some smart way]

and thereby covering all the needs with one line. Is there some clever way to do this currently? 

That is exactly what I was referring to in my last reply. Automation rules have smart values for exactly this, but as I mentioned, a smart value to retrieve the component lead is not supported yet. While there is a feature request to make this possible, check the related thread I shared earlier for a possible workaround. 

[Sandra.Abi-Khalil]

Ah, I understand.

As far as I could tell from that thread they're literally suggesting to do what I mentioned I would have liked to get out of, which is to create an automation rule by manually listing every single application and assigning the component lead for each of them:
--------------------------
If Components equals [Application1] -> Edit issue field [Component Lead] to [Adam]
If Components equals [Application2] -> Edit issue field [Component Lead] to [Betty]
.
.
If Components equals [Application100] -> Edit issue field [Component Lead] to [Zeus]
--------------------------

But please let me know if I seem to have missed something - if not I guess I'll just press on.

Thank you for all your help!

[Sandra.Abi-Khalil]

Follow up question, since I seem to have to set up an automation rule to try to do this: Is there a way to access the Component Lead field that I set up in the Component?

So, since I have about 100 applications I really don't want to have to set up a rule with this structure:
If Components equals [Application1] -> Edit issue field [Component Lead] to [Adam]
If Components equals [Application2] -> Edit issue field [Component Lead] to [Betty]
.
.
If Components equals [Application100] -> Edit issue field [Component Lead] to [Zeus]

It would be far easier if it were possible to go:
If Components is not empty -> Edit issue field [Component Lead] to [Copy from Component in some smart way]

and thereby covering all the needs with one line. Is there some clever way to do this currently? 

[Thuan_ Do Dang]

Hi @Sandra.Abi-Khalil ,

To auto assign issue to Component Lead, you have to select Automatic on your Assignee field.

After you set Component to your issues, you can use bulk change to bulk update your issues's assignee to Automatic.

[Sandra.Abi-Khalil]

But doesn't that populate Assignee with the registered Component Lead in new issues?

I want to populate the field Component Lead with the registered Component Lead in the Component, when there is a Component in an issue.

Our Component Leads aren't going to be assigned the work, they are our contacts for questions regarding the respective applications.