Responders field in JQL

[Erin Blomert]

Has anyone found a way to use this new field with queues?  I see that I can add "Responders" as a column, but I can not search if it is empty or if the current user is in that field, etc.

The ultimate queue would be if the current user is in a group that is in the Responder field... Should I keep dreaming?

Thanks!

[Angélica Luz · Accepted solution]

Hello @Erin Blomert,

Thanks for reaching out to Atlassian Community!

The field Responders is currently not supported in JQL, therefore it’s not possible to add it to queues or save it on a filter.

There is a feature request suggesting this ability:

• Make Responder Field Type supported by JQL

Please, click on vote and also watch the ticket to receive future updates from our product managers.

Kind regards,
Angélica

[Erin Blomert]

Thanks for the link, I'll be following the ticket!

[Jack Brickey]

Hi Erin, I am not familiar with this field and it does not exist in my instance. Is it possible that this is a custom field (admin > issues > custom fields)? Can you educate me on this field?

[Jack Brickey]

So actually I do see it as you suggest as an option in queues. I am intrigued, let me poke around a bit.

[Jack Brickey]

Ah so this is associated with Opsgenie - what-are-responder-alerts and the field is associated with Incidents. 

[Erin Blomert]

Hi @Jack Brickey - yeah, it's the new Opsgenie integration field.  Seems pretty basic so far - a Jira field you can't use in JQL???

[Jack Brickey]

I don’t use OG in an integrated manner but I suspect this isn’t a Jira field but an OG field.

[Erin Blomert]

As of a couple of weeks ago, it can be added to screens!  I am still playing with it, but it almost seems as though it should replace "Assignee" on an Incident type ticket.  Definitely not there from a functional standpoint, though.

[Jack Brickey]

As I am intrigued by your question and situation here I’m going to try to bring it to the attention of some Atlassian colleagues that might have a more official response for you.

[Erin Blomert]

Thank you so much!