How to auto assign issues to different project leads using same workflow in separate projects?

[Divjyot Puri]

I have two separate projects and both of them are having two different Development leads. However, both the projects are using same Jira workflow. I want to assign the tickets to respective Development leads for "Code Review" using post function. What is the best way to implement it as we are not using components?

[Nic Brough -Adaptavist-]

This cannot be done (as described).  An issue belongs to a single project, and, rightly, can only ever have one assignee.

I suspect what you are trying to do is not have one issue.  I suspect you want to clone an issue into a second project, and assign it to the other project lead.

You will need to use one of the automation or scripting apps to set that up.

[Divjyot Puri]

@Nic Brough -Adaptavist- Let me explain:

We are using scrum and this is our structure

------------------------------------------------------------------------------------------------

Project 1: Team 1

Workflow used - XYZ

Dev Lead: ABC

When status is changed to "Code Review" I want the issue that is created in Project 1 to change assignee field to "ABC" automatically using post function.

-----------------------------------------------------------------------------------------------

Project 2: Team 2

Workflow used - XYZ

Dev Lead: DEF

When status is changed to "Code Review" I want the issue that is created in Project 2 to change assignee field to "DEF" automatically using post function.

-----------------------------------------------------------------------------------------------

I don't want to clone issues/tickets from one project to another. All I want is that the assignee field should get updated to respective "Dev Leads" in their respective projects.

Let me know if you need more clarity around it.

Thanks!

[Nic Brough -Adaptavist-]

So why have you confused this with two projects and different people and stated that you want one issue?

It now sounds like the talk of separate projects and people is irrelevant.  Your need is "assign the current issue to the development lead when it goes to a certain status"

You will need to use one of the automation or scripting apps to create such a post-function.  It will need to read from where-ever you are storing "who is development lead" and copy that to the assignee field.

[Divjyot Puri]

@Nic Brough -Adaptavist- 

Okay. So, if I create a User picker custom field that stores the name of the Dev Lead and then apply post function on transition to copy Dev leads name from that custom fields and assign its value to Assignee field, will that work?

Also, just want to confirm that issues in one projects are completely mutually exclusive and doesn't have impact on each other, right? In other words, using the above mentioned post function will look for Dev leads name within the project the issue was created in and would not copy data from other project, right?

I am new to Jira, hope I am not asking too many questions.

Thanks for the help.

[Nic Brough -Adaptavist-]

Yes, a custom field copied to the assignee is the most simple and clear way to do this.  Spot on!

Issues in different projects are completely independent themselves.  They may share common data (Links, Epics, selections in fields, etc), but updating one issue will have no effect on another (unless you've added code to do that)

[Divjyot Puri]

Cool! Thanks for the clarification.

Our previous Jira Admin had created a Multi-User Picker custom field for Dev Leads(that contains only one name only at a time) which I was trying to re-use. Is there a way we can set its default value? so that when a new issue is create this fields automatically stores the name of respective Dev lead depending on which project the issue got created from.

[Nic Brough -Adaptavist-]

I don't think you can - you don't have information stored as to who the lead should be for each project, so there's nothing to work with.

[Divjyot Puri]

@Nic Brough -Adaptavist- I figured that out on my own, here are the steps to set default values for custom fields:

Open the Project -> Open an existing issue -> Click on Actions icon (...) -> Click on Configure option -> Select Custom field from left menu -> Search your Custom field ->  Click on Actions icon (...) for your Custom field -> Select Context and Default Value -> There you can add separate default values for separate Projects.

Hope this information is helpful and enhances your knowledge too.

Once again thanks for the help.