Unassigned vs No Resource Defined

Christine Herman

We have several Jira tickets that are unassigned because no resource has been defined (maybe it is in the backlog or we need to hire a new resource).  Have you found a way to differentiate the tickets that have not yet been assigned because of those reasons, versus those that just haven't been reviewed for an assignment?

Ollie Guan

Hi @Christine Herman,

Provide some solutions and hope to help you

1. Create a virtual user, such as an unknown resource, assign these questions to him, then use unknown resources and unassigned to filter
2. Customize a field to mark it, or mark it with a label
3. Add a state to the workflow configuration. When there is no resource to process the Issue, the flow goes to that state.