Is there query in JQL where it would show a list of issues where the assignee was NOT changed when it was initially assigned to a user? These are Jira Service Desk issues and there is not a default assignee when the issue is first created. So, for this JQL, I would need to see those issues that were only assigned once and then resolved with that same assignee. Any ideas? Thanks!
@Lindsay Czopur Give this a try...
assignee is not EMPTY AND NOT assignee changed BEFORE now()
@Jonny AdamsThanks! While that did work to pull issues that had NO change in assignee whatsoever, it looks like from our issue history that to get full scope, we need the assignee to only change ONCE. That appears would be a more accurate search, but I still don't know if I would be able to tell that from JQL. Any thoughts would be appreciated!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Lindsay Czopur I think this task is beyond the scope of JQL. Unfortunately, there is no JQL for "current assignee". JQL also doesn't support historical searches for certain user fields.
If you typically have service desk agents passing issues back and forth you could work that into your workflow. One option would be to add a status in your workflow to reflect an escalated issue (status=escalate). You could restrict the assign permission throughout your workflow and simply auto assign on transition to the Escalate status. (If you are looking for balanced auto assign to a group then you may want to look into ScriptRunner or Automation for Jira.)
Then you could perform a JQL query to disclude any issue that was in the Escalate status at any time and sort by user to find all issues that were resolved by the original assignee.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Jonny Adams, I figured as much, which is why I wanted to see if the community knew anything I didn't! We actually do use an escalated status in a different way, so that won't work for this particular case. It was a "nice-to-have" so I'll at least let me team know. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.