Skip to content

Assignee/Reporter subscription filters show no options (Jira Cloud OAuth) — same field works in Create Issue modal #1337

Description

@piotrsz0772

Plugin version: 4.8.0
Mattermost: Entry Edition, self-hosted
Jira: Jira Cloud, instance type cloud-oauth

Summary

The "Assignee" filter added in v4.4.0 (#1112) never populates its value
list in the Edit Jira Subscription modal. The dropdown stays empty and
the generated JQL renders as "Assignee" IN ?.

The same field resolves correctly in the Create Jira Issue modal, where
the full user list loads without typing — so user search itself works.

Steps to reproduce

  1. Connect a Jira Cloud instance via /jira instance install cloud-oauth
  2. Run /jira subscribe, pick a project and issue type
  3. Add a filter, choose field "Assignee"
  4. Open the value dropdown — no options, typing returns nothing
  5. Run /jira issue create in the same instance, open the Assignee
    field — the user list loads correctly

Expected

Assignee filter offers the same user list as the Create Issue modal.

Actual

Empty dropdown; JQL preview shows IN ?.

Ruled out

  • OAuth 2.0 (3LO) scopes: read:jira-work, read:jira-user, write:jira-work
  • Global permission "Browse users and groups" granted to the account's groups
  • Not a stale webapp bundle (hard refresh performed)

Suspected cause

The subscription filter component appears to build options from
allowedValues in createmeta. Jira returns no allowedValues for
user-type fields — only autoCompleteUrl — so the list is always empty.
The Create Issue modal uses a live user-search endpoint instead.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions