Webhooks for components to reduce load on Jira

Jira Development Jira Cloud
1

We’re implementing an app which would like to react to changes to components. Whenever a component is created, renamed or deleted, we want to process this change & synchronize it to another Jira instance.

With the current possibilities in Jira Cloud what we can do is:

  • Poll the complete component list periodically
  • Analyze what components have actually changed
  • Make modifications accordingly

My problem with this approach is that it places additional load on the Jira instance and our backend to query periodically (and probably often for no changes). With Atlassian’s initiative to look closer at rate limiting apps, this approach is also not ideal.

Probably as a request to Atlassian: Would you please consider adding webhooks for components? On Data Center, there are the ProjectComponentEvents. It would be great if these could be exposed via a webhook similar to versions. I haven’t found a Jira issue for this yet, but I’d appreciate to see one created.

If someone else has a clever approach to this ticket, I’d appreciate your thoughts.

Cheers,
Matthias.

2

We also need this for our Version & Component Sync Cloud app that is currently pending release and will be available shortly. Our current implementation uses the polling, but it would be a lot easier (and cheaper for us) if we can have component events & webhooks.

Even better would be if this is implemented generically and component events are also added to the on-premise code base (DC), because ultimately, the lack of component events in Server product is the reason we also do not have them in Cloud

3

Hi @matthias and @remie ,

Thanks for the idea. I’ve created the following feature requests:

Regards,
Dugald

4

Hi @dmorrow we are also highly expecting this feature, however, I have seen that your first ticket is closed due to duplication and the original ticket has unfortunately no traffic.

best, Valentin

5

Hi @ValentinPravtchev ,

Thanks for your feedback. Development teams look at the number of votes for each issue as a signal for prioritisation so make sure you vote for the issues.

Regards,
Dugald

6

Hi again @dmorrow thanks for reply! Where can I vote for the issue?! I do not have seen any button in the issue!

However, I liked the above posts. Maybe thats sufficient?!

Best Valentin

7

@ValentinPravtchev - liking this post is a great gesture, but it won’t be considered in any future plannings, I’m afraid.
You can vote for the issue by pressing the thumbs up icon in the top left corner.

vote
vote1719×1303 290 KB

This way, it’s at least easily accessible by the corresponding Atlassian team.

EDIT: I’ve just realized that I shared a screenshot for the duplicated issue but I think you got the idea. :slight_smile:

8

Hi @matthias thanks and I have voted for the issue ! Hope that there will be any progress in near future!