nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

No invite email being sent after adding customer to Project via API.

unknown

I have an integration setup which utilizes the API route /rest/servicedeskapi/servicedesk/{serviceDeskId}/customer to add a user to one of my Projects. It accomplishes that fine, but it does not send the user a notification that they have been invited.

Is this intended functionality that invite emails are only sent when adding customers to a project via GUI? Or is this something yet to be implemented or a problem on my end?

Accepted answers

Kai Becker

Hi @[deleted],

I'm not fully aware of what you are trying to achieve, but I think there might be a misunderstanding.
The REST endpoint you mentioned (besides that it is experimental) only adds existing customers to a JSM project, so that they can create requests. As fas as I know, an invitation mail is only sent out, when the customer is initially created and not, when is being added to another project.

Maybe you could explain the use case a little bit more?

All comments

Kai Becker

Hi @[deleted],

Maybe you could explain the use case a little bit more?

unknown

Thanks @Kai Becker

The main goal of my integration is to create a customer with access to my service desk and notify them about it.

So first I create the customer with /rest/servicedeskapi/customer but no notification. So then I thought, maybe they need to be added directly to a Service Project (/rest/servicedeskapi/servicedesk/{serviceDeskId}/customer) in order to get an email invite.

The reason I thought the second route would trigger an invite email is that a customer gets that invite email if I give them access to my service project directly via GUI. But, as stated above, via REST, they do not. I'm wondering if this is intentional, or if it is simply an oversight or not implemented since the route is experimental as you say.

Kai Becker

Hi @[deleted],

I just scrolled through the API documentation. It's noted, that no invitation mail is sent

I then thought it might be a solution to create customers via automation, as this could also be triggered via webhook:

Screenshot 2022-03-14 at 22.07.26.png

curl:

curl -X POST -H 'Content-type: application/json' https://automation.atlassian.com/pro/hooks/123455 --data '{"username":"testcustomer", "email":"testmail@example.com"}'

But notifications are not sent there either. There is an open request for this: https://jira.atlassian.com/browse/JSDCLOUD-10154

The only workaround would be to trigger an extra email after user creation. This way, they will get an info about their created account, but they won't be able to login, as there is no password set. So they need to go through the password reset process after that.

This seems really inconvenient

unknown

Ah, that's an unfortunate answer...

But thank you @Kai Becker for digging into it and pointing me to that open request. At least I can add my vote.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management