Secondary flow webhooks

Jira Development Jira Cloud
, ,
1

Hello,
I want to validate under which conditions a comment_deleted event would be sent with a secondary flow header. Is it only when the parent issue is deleted?

Additionally, can you expand on the “etc” in

All Secondary webhooks are a result of long-lasting bulk or cascade operation (bulk issue update, project deletion, issue deletion etc.)

from the docs?

2 Likes
3

Hi @jbevan ,

My interpretation of the documentation is that the comment_deleted event would have a Primary X-Atlassian-Webhook-Flow header only if that comment was directly deleted, but a Secondary flow header if some other operation resulted in the deletion of that comment. Based on this, two other operations that would result in the comment_deleted event firing with a Secondary flow header are project deletion and parent comment deletion. The “etc” in the docs refers to entity events that imply other entity events (e.g. the deletion of a project implies the deletion of all issues in that project).

EDIT 29-Mar-23: Jira doesn’t have comment threads so “parent comment deletion” doesn’t make sense.

Your request has been forwarded to a Jira webhooks expert to check this.

Regards,
Dugald

4

Hello!
I think currently the comment_deleted event will be sent when deleting issue/project.
Cheers!

5

The “etc” in the docs refers to entity events that imply other entity events (e.g. the deletion of a project implies the deletion of all issues in that project).

Is there any chance Atlassian could document these in case we’re unaware of something? My lack of knowledge of all of Jira Cloud has caught me out a few times.

1 Like
6

@TomaszKanafa ,

I think currently the comment_deleted event will be sent when deleting issue/project.

I agree and tested this to be the case when a project is deleted. In that case, the flow header was "x-atlassian-webhook-flow": "Secondary".

@jbevan ,

Is there any chance Atlassian could document these

I clicked the “Rate this page” stars which opened up a simple dialog allowing me to provide feedback. This is the feedback I entered:

On this page, there is text as follows:

“bulk issue update, project deletion, issue deletion etc.”

It is suggested that “etc” be replaced with the remaining types of events that can cause cascading events or that the general rules be explained such that developers can deduce what these events are.

This feedback feature is available to everyone, but it unfortunately doesn’t return a reference to an issue that can be tracked.

Regards,
Dugald