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

Issues automatically getting unnassinged when resolving tickets

Nickolas Dinnan

whenever someone resolved a ticket for whatever reason the ticket then gets unassigned i tried to add a post function to the resolved status to auto-assign but it doesn't appear to be working

Accepted answers

All comments

Jack Brickey

Are you saying you want to set to unassigned or you are trying to stop this from happening? Either way hopefully the following helps...

Two possibilities for the cause:

there is a post function on the resolution transition(s) that is clearing the Assignee. I have seen people do this because they feel that no one should be assigned a closed issue. Not a fan but I get it.
automation - someone has set up an automation to clear the assignee. again for the same reason.

Nickolas Dinnan

i have added post functions to auto assign to the current user and also created automation rules to assign to user who triggered transition into resolved status.

neither is working

Jack Brickey

so something clearly is clearing the Assignee field after the fact. If you have a post function to set the Assignee on the transition you are in fact using then the clearing is happening after your PF executes overriding your action.

would you mind sharing the post function view for any transition into Done (or whatever status we are talking about here).

Nickolas Dinnan

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk