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; } } }

Jira webhook doesn't return assignee email

Dan_vktmy8

a few days ago our php emailer stopped working. It works by generating emails whenever a webhook is called. The webhook is called whenever we drag an issue from one place to another.

after digging i found that the JSON sent to the php script no longer contains the assignees email address (issue->fields->assignee->emailAddress).

I did however find that if i drag an issue that is assigned to me it does contain my email in the assignee data.

Accepted answers

All comments

Dario B

Hello @Dan ,

The behavior you are reporting seems related to the introduction of the new Profile and Visibility settings:

Update your profile and visibility settings

In short: this change was needed in order to comply with GDPR. As a result, even if you don't see the email address, you should still be able to get the Public Name and the Account ID for the users.

This change has been widely announced and documented:

Major changes to Jira Cloud REST APIs are coming to improve user privacy (May 2018)
Major changes to Atlassian Connect APIs are coming to improve user privacy (Jun 2018)
State of Atlassian Ecosystem changes to address privacy (February 2019)
Upcoming changes to Atlassian account profiles (May 2019)

Guidelines for developers are available in the below threads:

Also, be aware of the below bugs when handling non-managed users:

Please review the above links and let me know if you have further questions on this topic.

Cheers,
Dario

Dan_vktmy8

I made my email public as i suspected this was the case but still nothing gets returned in the email field if someone else updates an issue related to me.

Dario B

Hi @Dan ,

I have just tested this and for unmanaged accounts I am actually always able to get the email address.

I have set my WebHook to be triggered on issue created or updated events and I am using https://beeceptor.com to test it.

Now, since this is working fine for me, can you kindly provide more details on what you have done? E.g.:

Are you testing this using managed or un-managed accounts?
Which events are triggering the WebHook?
Do you use any JQL query to filter events, or all the issues are returned?

Please let me know.

Cheers,
Dario

dlozanolu

Hello Dario,

I have the same problem. Is there any way to make it work again like before?

Welcome!

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

Quick Links

Find more posts tagged with

jira

webhook