Turned out to be an actual but, new report creatd here: https://jira.atlassian.com/browse/ECO-1112
Used with @forge/cli 12.6.1.
When using JSM & having portal-only customers, only avi:jira:created:user is triggered.
When using JSM, a portal-only customer should also trigger following events:
avi:jira:updated:user:- when portal-only customer updates themselves their profile from within portal (display name, email, timezone) OR
- when portal-only customer is being updated through admin.atlassian.com (Apps > Sites > given site > Jira Service Management > Portal only customers) eg.: "Edit full name".
avi:jira:deleted:user:- when portal-only customer is being deleted through admin.atlassian.com (Apps > Sites > given site > Jira Service Management > Portal only customers).
If above events are not suited for portal-only customers, then an alternative events for portal-only customers should exists.
Setup:
forge registerforge deployforge install -p Jira -s yoursite.atlassian.netforge tunnel
Reproduction steps:
- Sign-up with new user to your's site service desk (https://yoursite.atlassian.net/servicedesk/customer/user/login)
- ✅
avi:jira:created:useris triggered
- ✅
- Head to https://yoursite.atlassian.net/servicedesk/customer/user/profile, and update your personal details, such as display name.
- ❌
avi:jira:updated:useris not triggered
- ❌
- Head to site's admin console (admin.atlassian.com), go to Apps > Sites > given site > Jira Service Management > Portal only customers, find your newly created user and delete the account.
- ❌
avi:jira:deleted:useris not triggered
- ❌