Assignee is being automatically assigned via Component. How do I automatically assign Dev lead?

[odcsqa]

We have two fields defined. Assignee which is correctly being assigned issues based on Component (as the Component Lead). But we have a 2nd field called 'Dev Lead' who is generally the Development Manager that the Component Lead is reporting to. (NOT the Project Lead). How do I set this up so that the Development Manager is automatically assigned as well based on the Component selection? So for example:

Joe owns Component X

Dave is the manager of Joe and also of Component X

QA person enters an issue and assigns it to Component X and Joe becomes the Assignee, as expected.

How do I set the Dev Lead field to Dave?

[Nic Brough -Adaptavist-]

Assignee is a single user, it is intended to be the single point of responsibility for the issue (at the current time).  Believe me, you really do not want more than one of these, it does not work, and you will regret any attempt to have multiple assignees.

To get your develpment lead copied into the development manager, you will need to look into automation or coding, so that you can implement the rules you need for that association.

This means getting a scripting or automation application (I suspect scripting here, as it's not as simple as "if X, then fill field with Y", you've got more than one simple question to ask)

Do you have an automation or scripting app yet?

[odcsqa]

It is for certain that I want a dev manager listed as the Dev Lead in issues separately from the Assignee and I definitely will not regret it.

Whether it needs to be automatic or by manual process is still up in the air. If the way JIRA works makes it a bad idea to try to do it automatically then I would do it manually by process. (But was hoping not to have to do that).

So there is no way to do this with a Post Function or something along those lines?

[odcsqa]

Issue: My Issue

Component: X

Component Lead of X / Assignee: Joe the developer

Dev Lead: Dave the manager

Component X issues are always owned by Joe by default. But Dave's queries will include Component X issues along with Components Y and Component Z plus any issues that are not associated with his components X, Y, and Z but that he was manually made the Dev Lead on anyway. They all will show up in his queries together based on one field: Dev Lead.

[odcsqa]

For more background, our development managers have always had a very hard time creating queries of the issues they are responsible for because:

1. they own most of the issues in their components but not all of them

2. they own most of the issues their people are assigned to but not all of them

3. they also own a few issues that are neither in one of their components nor assigned to any of their people.

Having a default Dev Lead for Components assigned to these dev managers would at least get them most of the way there and then manually setting the Dev Lead on the rest of them will finally provide them with the ability to create queries of all the issues they are responsible for driving.