Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Specifically, this affects users like this one, who are not in a group like jira-users blessed with 'Application access':

The 'helpdesk' user here is, per Crowdsourcing triage: A useful pattern for Jira issue ownership, an account that never logs in but does get emailed.

What should happen if a new issue is created, assigned to 'helpdesk', or with 'helpdesk' as a watcher?

  • Well, in In Jira 8.13.x, a notification would go out to [email protected]
  • In Jira 8.20.x no notification goes out.

The 8.20.x behaviour is actually correct. An account without Browse permission shouldn't get emails. Yet this important bug fix is not listed in the release notes, nor in the [174 bugs fixed between 8.13.1 and 8.20.1|one of the

Jira
serverAtlassian JIRA
jqlQueryissuetype=Bug AND project in (JRASERVER,JSWSERVER) AND fixVersion in ('8.20.0', '8.19.1', '8.19.0', '8.18.2', '8.18.1', '8.18.0', '8.17.1', '8.17.0', '8.16.2', '8.16.1', '8.16.0', '8.15.1', '8.15.0', '8.14.1', '8.14.0', '8.13.12', '8.13.11', '8.13.10', '8.13.9', '8.13.8') AND status in (Resolved, Closed, Soaking, "Released to Server") ORDER BY votes DESC, priority DESC, key DESC
counttrue
serverId144880e9-a353-312f-9412-ed028e8166fa
]
fixed between 8.13.1 and 8.20.1 - at least, that I can see.

Anyhow, to know whether your Jira has any user accounts like this, run the following SQL (Postgres-flavoured):

Code Block
select user_name FROM cwd_user JOIN cwd_membership ON child_id=cwd_user.id JOIN cwd_group ON cwd_group.id=cwd_membership.parent_id WHERE cwd_user.active=1 AND cwd_user.id not in (select child_id from cwd_membership JOIN licenserolesgroup ON licenserolesgroup.group_id=cwd_membership.lower_parent_name);

If you get output, that's bad - those users will stop getting emails in 8.20.x+. Time to fix your group memberships, or bless the group your users are in (here 'MyCompany') with application access.