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

Default assignee cannot be overridden at issue resolving

Anton Kuzmin2

As developer I finish working on issue and want to resolve and assign it to our tester (I choose him in popup) with 1 action. By default, reporter (analyst) gets issue back on resolving, so I have to resolve and then assign issue to the correct person.

Jira version: v4.4#649-r158309

Accepted answers

All comments

Aspect Infra Te

your jira admin need to create tansition changing resolution with screen containing field "assignee"

Anton Kuzmin2

Admin says it's already done. See attached screenshot.

Aspect Infra Te

ok so assignee field should be on "resolve issue screen"

Anton Kuzmin2

My admin says you misunderstood the problem.

Ivar

What do you mean with 'gets issue back'? Is the problem that you cannot resolve the issue and assign it to the tester? Or is the problem that your choice for assignee is automatically set to the reporter, no matter who you assign it to

Anton Kuzmin2

@Ivar
Yes, no matter who I assign issue to during resolving, it always gets back to the creator of that issue (reporter).

Ivar

Most likely there is a Post function active that says 'Assign to reporter' when the issue is resolved. Ask your administrator to check the workflow for post functions in the transition from 'in progress' to 'resolved' or whatever the step after 'in progress' is called.

Ivar

The it sounds like there is a setting in the workflow that overrides this. Ask your administrator to check if there is a Post function 'Assign to reporter' active in the workflow.

Anton Kuzmin2

Yes, it it active. What's the point in asking 'assignee' during resolving then? In my opinion, logically, if user can set assignee, then it must overwrite any post functions.

Ivar

I would say either is wrong. And I would say that default assigning something that hasn't been verified by QA is wrong (at least for development issues). My suggestion would be to change the workflow and introduce two transitions when an issue has been fixed (naming from the top of my head):

Ready for QA
Resolved and Closed

Depending on the issues nature you either assign it to QA for verification or you assign it back to the reporter. If 'ready for QA' you as developer can choose asignee. If 'resolved and closed' Jira can automatically assign to the reporter. 'Resolved and closed' can also be the transition QA can choose when the issue has been verified. E.g. the asignee is automatically chosen as the reporter.

Sean Kane

I had the same problem with the Resolve screen. Since that option was not overriding the workflow I used the Field Configurations>View Field Configuration to hide the assignee option from the Resolve screen.

unknown

This is not what the OP is asking for. I want what they want as well.

The problem is JIRA only allows the POST transition to assign to either a Lead Developer, Assignee, or Reporter. Most organizations I've worked in the is also a QA lead who need to regress the fix and verify it as fixed/closed. Often that person is the reporter, but not always as sometimes developers file tickets and so do non-dev folks. So JIRA either needs to be able to assign to an arbitrary user, or to create a Lead QA role and make that assignable in the project settings, then using the POST transition feature here be able to post to that person.

At present, it is very inflexible for real-world work flows.

Welcome!

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

Quick Links

Find more posts tagged with

jira

assign

resolve