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; } } }

'Updated' issues are being automatically assigned to the Project Lead unexpectedly

Nicole Gosling

I, Nicole created a new workflow step called 'To Be Verified' which is available when the ticket is 'Inprogress'. When this is the current status there are two buttons available for the user to select -- 'Verified Fixed' and 'Not Verified Fixed'. I created a Post Function transition - 'Assign the issue to the default user from the Business Analyst role.' but did not select 'Skip if Assignee as I am the only BA that manages incidents for this project. Paul Frank (Project Lead) and myself are the only members of the Business Analyst group I am set as the default user.

When the user selects 'Not Verified Fixed' she get the workflow screen, which includes the Assignee and Comment field. She doesn't change the assignee; enters a comment and clicks the 'Not Verified Fixed' button. The tickets is automatically assigned to Paul Frank. I expect that it would be assigned to me based on the Post Function that I added to that step.

I have tested different scenarios but the one that was most surprising was when I added myself as the Project Lead and set the default assign to unassigned and it still assign to Paul Frank. What other setting could be causing this to happen? Is this a bug in the system?

Accepted answers

Nicole Gosling

JIRA has no concept of a "default assignee" at the role level. You must do the work of telling JIRA who this person should be. Without giving JIRA and the plugin that is controlling this post-function the information about who to assign, you will continue to get unknown/unpredictable results that we cannot troubleshoot. Please add the followin properties to your user:

Go to Administration
Users
Click on your username
Click Edit Properties at the bottom of that page
Add the following:
- Key: defaultAssignee
- Value: MUP -> Business Analyst

All comments

Jo-Anne MacLeod

You said that you are part of the business analyst group, but didn't mention if you are in the business analyst role for the project. My guess is that you are not in the role. Verify in the project by looking at "people" and checking out the roles. If necessary add yourself into the role.

Nicole Gosling

In response to Jo-Anne MacLeod's response dated 04/13/2012 02:50 PM. I am a member of the business analyst group which is assigned the business analyst role. In my permission scheme I assigned roles not groups or users

Ramiro P

I think I know what is happening, I've been trough the same thing. Do you have that issue related to a component? If that's the case, check if Paul Frank is the Component Leader, and if it is you can set it to 'By Default' and then it will be possible to assign other persons.

Nicole Gosling

I have confirmed that for all Componetns there is no Component Leads assigned and the Default Assignee is set to 'unassigned'

Ramiro P

Mmh.. Ok, What role on the project has Paul Frank when you put yourself as the project leader? Is he still in the project?

Ramiro P

In the administration section, can you see into Roles and 'Manage members by deafult' in the BA role? There will show you the users that are from that role by default, is there Paul Frank or other user? If Paul Frank is the only one in the list or the first of the list, then that's the issue.

Nicole Gosling

Go to Administration
Users
Click on your username
Click Edit Properties at the bottom of that page
Add the following:
- Key: defaultAssignee
- Value: MUP -> Business Analyst

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud