nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project lead not getting assigned to issues

unknown

When creating an issue, we´ve set it so that the project lead gets assigned to the issue automatically. Recently it gets assigned to one of our administrators and not the project lead.

Screenshot 2021-06-02 161023.png

What needs to be done so that the "Spoc" gets automatically (without automation seetings) assigned to the issues?

Thank you in advance!

Accepted answers

Lyanh Hoon

I have the same issue in Jira Service Management. There's no component set up or post-function to auto-assign issues. @[deleted]Were you able to find where the problem was that you could share?

All comments

Niranjan

Hi ,

Check the workflow post-function of Create Issue transition.

If the issue has component field value, check the components page in the project(if issues with components has default assignee)

unknown

I´ve checked the field configuration scheme (which is the same as in other projects) but in that project there doesnt occur this problem with the project lead

Daniel Ebers

Hi @[deleted]

is there any chance the component setting of default assignee is overriding your settings - to check could you check if there are components set to the troubling issues in question and if so, if there are settings for components which could be responsible?

https://confluence.atlassian.com/adminjiraserver/managing-components-938847187.html

I am assuming so because:

Components are sub-sections of a project. They are used to group issues within a project into smaller parts. You can set a default assignee for a component. This will override the project's default assignee, for issues in that component.

Regards,
Daniel

unknown

Screenshot 2021-06-07 083732.png

Hi @Daniel Ebers thank you for your reply!

actually on ALL projects there were automatically given those two components by jira servicedesk (we didnt create any other). And all are assigned to the project default.

Regards!

Daniel Ebers

So - just for a summary and a better understanding, you still see some other user than "SPOC" assigned when a Component like "Öffentliche Website" is selected, is this right?

If so and no setting via component lead + no setting via project default is taking place + no setting via workflow is done - only some sort of automation, possible via an App comes to mind.

unknown

Do you mean to solve the problem via automation setting or to check if automation is set?

Lyanh Hoon

I have the same issue in Jira Service Management. There's no component set up or post-function to auto-assign issues. @[deleted]Were you able to find where the problem was that you could share?

unknown

Hi @Lyanh Hoon

yes the Jira support was able to help me through it.

The problem was that in the "request types" one user was set as Assignee (dont ask me how, I didnt do it)

So when you check request type, there will be a hidden assigned field and if that has a present value with the user name you just have to remove him/her so that the next created issues will be assigned to the project lead.

Hope I could help you

Lyanh Hoon

@[deleted]Thanks for sharing. Yes, I was able to find that there's an assignee field in the Request Type set automatically by Jira that caused the issue.

Thank you!

unknown

I´m glad I could help, you´re very welcome

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-service-desk

customer-portal