Project Lead being Assigned Tickets when they're Updated

Jonathan Holmes January 23, 2017

Hi,

When a ticket is raised it comes through as "Waiting".  We then assign the tickets to the users using the "Assignee" function and selecting the relevant user, but if the user then updates the ticket, the ticket is automatically assigned to the project lead and they have to manually find the ticket and re-assign it back to themselves.  (The users do have the 'Assignable User' permission)

If the user presses "Take Ownership", then updates the ticket, there is no issue.

Why would JIRA automatically assign the ticket back to the project lead, when we have assigned the ticket to a specific user?

These are the specific Post-Functions on the relevant transition for "Email Customer" at "Waiting" status.  There isn't anything relating to the project lead here apart from potentially number 2?

  1. Set issue status to the linked status of the destination workflow step.
  2. Assign the issue to the current user. Please note that the issue will only be assigned to the current user if the current user has the 'Assignable User' permission.
  3. Add a comment to an issue if one is entered during a transition.
  4. Update change history for an issue and store the issue in the database.
  5. Re-index an issue to keep indexes in sync with the database.
  6. Fire a HSD - Status Change event that can be processed by the listeners.

Thanks,
Jonno 

 

1 answer

0 votes
Vasiliy Zverev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 23, 2017

It could be caused by some listener. 

Try to investigate your listeners which could do these changes.

Suggest an answer

Log in or Sign up to answer