Set up GitHub ⇔ Jira connector

[chadwhitacre]

To support #42 we want to set up an automation that creates a shadow Jira ticket for issues in the sentry GitHub repo. The purpose of the Jira ticket is to integrate with our existing customer tagging/tracking infrastructure, as well as our sprints and planning for EPD. Most comments and content should stay on GitHub. Ideally we wouldn't create a Jira for every GitHub, but only when we want to start doing something with it in Jira (tag a customer, bring it into a sprint, etc.(?)).

Requirements

1. When someone applies Trigger: Create Jira Ticket
   1. Check the description for a link to an existing Jira.
   2. Create a new Jira if it doesn't exist, and link it in the description.
   3. Remove Trigger: Create Jira Ticket
2. When resolved in Jira.
   1. Close on GitHub.
3. When unresolved in Jira.
   1. Reopen on GitHub.

To Do

• Evaluate options, integration vendors vs. diy with eng-pipes.
• Pin down requirements.
• Investigate Unito a little more.
  • Understand permissions.
  • Try to guess how it will break for us.
  • Pin down pricing.
  • Have a call with Unito.
• Submit SaaS intake.
• Go through legal / security review.
• Buy Unito.
• Do a little label maintenance.
  • Add Sync: Jira label sentry#42447
  • Tweak Trigger: labels sentry#42452
    • This is a sidebar, but I'm thinking of Trigger and Sync as cousins and want to use the same color.
• Configure Unito in sentry.
  • Install Unito on GitHub.
  • Install Unito on Jira.
  • Put the thing in Advanced Options to avoid status jump on unlabel.
• Add to remaining repos.
  • self-hosted
  • sentry-docs
  • relay
  • sentry-javascript
  • sentry-php
  • sentry-python
  • sentry-react-native
  • sentry-laravel
  • sentry-cocoa
  • sentry-dart
  • sentry-dotnet
  • sentry-java
  • sentry-native
  • sentry-ruby
  • sentry-symfony
  • sentry-unity
  • sentry-android-gradle-plugin

[BYK]

Sounds like you may wanna try Pipedream out.

[chadwhitacre]

Yeah, maybe! I saw when you first linked that a while ago (probs on Twitter?). Are you actively using it?

[chadwhitacre]

Options:

• Pipedream
• Zapier
• eng-pipes
• ???

[BYK]

@chadwhitacre we've been using it at Formsort for many things and it works quite well. I think for Sentry's scale, you'd need to pay for the pro/team account up front as the daily limit of 66 invocations is a bit too low. The individual dev plan has more headroom for initial testing though.

We did build out that magical "automated changelog based on SaaS deploys powered by Jira tickets" thing we have been thinking about :)

[chadwhitacre]

Why should we use a nocode solution instead of eng-pipes?

[BYK]

It is not a no-code solution. You do write code but don't have to deal with the boring and error-prone parts like authentication, tokens etc. Arguably, you can probably replace whole eng-pipes with Pipedream workflows.

[chadwhitacre]

Link dump:

https://exalate.com/ppc-jira-github-integration/
https://marketplace.atlassian.com/apps/1218053/github-jira-two-way-sync
https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/

[chadwhitacre]

https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/ - doesn't apply, it only covers code on GitHub not issues

https://exalate.com/ppc-jira-github-integration/

https://marketplace.atlassian.com/apps/1218053/github-jira-two-way-sync => https://unito.io/integrations/jira-github/, I started looking at this a long time ago.

So that's Exalate and Unito in addition to Pipedream and Zapier.

[chadwhitacre]

Twitter Followers

Company	n
Zapier	70,253
Pipedream	6,524
Unito	1,067
Exalate	21

I checked, we don't already have any of these.

[chadwhitacre]

No-one ever got fired for buying Zapier? :o)

[chadwhitacre]

There's a "New Label in GitHub" event in Zapier but not afaict an "Apply label to issue" event.

[chadwhitacre]

Same with Pipedream, but there is a "create it" option.

[chadwhitacre]

I looked through Pipedream's issues and PRs and didn't see anything already in the works for this event.

[BYK]

@chadwhitacre I think you are looking for "New or Updated Issue (Instant)"?

It is essentially the same logic with GitHub actions: new/updated issue -> filter by update type & label