Default assignees when creating an issue

[Justin Carroll]

The issue we are seeing is that when we create a new issue in a project, the tech-lead and developer fields are being automatically assigned to a resource that is no longer on the project or in our Jira instance.  We have searched all through the permissions, schemes, workflows, etc and can't see where that is managed.  Anyone know if it is possible to change this behavior?

[Jack Brickey]

It seems you have already done some research but will mention just the same. It seems that these two fields are custom fields. So that rules out the project lead being used to set the assignee.

1. Inspect the create transition in the workflow for any post function that would set these fields. I would’ve thought this would be the answer but it appears you may have already looked at this in ruled it out?
2. inspect any automation rules under project settings.
3. is it possible that you have some add-ons that may be employed to accomplish this?

[Justin Carroll]

Thank you Jack. I looked at the post function (again) and it does have one that says the assignee will default to the developer value but this resource is not in the developer group (and it is a field that utilizes the user picker option.  There are no automation rules active on the project either. 

I tried to look at the custom fields which you are correct they are but those use the user picker selection tool as well so not sure why someone that doesn't come up in that list winds up being the default.  I created a test issue and assigned someone else and it still overwrote them with this old user.

[Jack Brickey]

4. check for a default value --> admin > issues > custom fields and look at "context and default value" under ellipses.

[Justin Carroll]

still no dice - can't find any default values entered