Email Notification using Forge UI

Forge Forge Custom UI and UI kit (beta)
,
1

We built an app using a Forge app developer. We have a requirement to send an Email notification to Jira users using the Email API.

Currently, our app is not listed on the Marketplace

Any help would be tremendous!

1 Like
2

Hi @IyyappanR,

I don’t think so Forge is supporting Email API at the moment.
More info: https://community.developer.atlassian.com/t/forge-emailing-api/51643

3

What are you trying to do. If you can connect it to an issue - there’s a notification end point that can be utilized. Otherwise you’ll need to find an external rest based service provider for email (however, you will have to jump through the hoops getting access to the email address of the user).

/Daniel

4

Thanks for your response @danielwester. if possible shall we connect in person to discuss further the requirement?

5

Hi @danielwester can you share some more details about that end point? :nerd_face:

6

@danielwester Having spoken to the team. The following is the use case. The team uses electronic signatures, and so when a signature is required, the user should receive an email. The ask here is how do they get an email service to a registered user of JSW?

7

What I was suggesting was to take a look at https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-notify-post

8

Thanks @danielwester for giving the link of REST API. Got 204 response status while calling the function form the forge apps. But didn’t receive any email regarding that actions.

please refer the below screenshot:

Response Screenshot
Response Screenshot1546Ă—155 7.57 KB

9

@danielwester @janambroz :wave: Please see above, have either of you seen this 204 error?

10

204 isn’t an error. 204 No Content is the expected response if the message is queued to be sent. See https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-notify-post-responses

11

Thanks @danielwester. It seems the message is being blocked and never comes out - does it matter if in development mode currently?

12

Don’t know. I think it ends up being Jira “magic” at that point. Check your settings to see if the user that you’re trying to send to is set up to send to (ie if you’re triggering at asUser and the user is has “don’t notify me on my changes” - then it might explain it).

Otherwise - don’t know - you might need to put in a dev support ticket.

/Daniel