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
- Connect a Jira Cloud instance via
/jira instance install cloud-oauth
- Run
/jira subscribe, pick a project and issue type
- Add a filter, choose field "Assignee"
- Open the value dropdown — no options, typing returns nothing
- 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.

Plugin version: 4.8.0
Mattermost: Entry Edition, self-hosted
Jira: Jira Cloud, instance type
cloud-oauthSummary
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
/jira instance install cloud-oauth/jira subscribe, pick a project and issue type/jira issue createin the same instance, open the Assigneefield — 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
Suspected cause
The subscription filter component appears to build options from
allowedValuesincreatemeta. Jira returns noallowedValuesforuser-type fields — only
autoCompleteUrl— so the list is always empty.The Create Issue modal uses a live user-search endpoint instead.