AppForShareOpen Integrations

Docs

Jira

Open a QA work item for every new build, with the install link in it, or a bug when App Store or Google Play rejects a release. Jira Automation receives the AppForShare webhook and does the rest, so there is nothing to install. Pro and Team.

  1. 1. Create the rule in Jira

    In your project open Project settings, Automation, Create rule (or Settings, System, Global automation for several projects). Pick the trigger Incoming webhook. Under "Execute this automation rule with" choose "No work items from the webhook". Jira shows a webhook URL and a secret: keep both.

  2. 2. Add the action

    Add the action Create work item, pick the project and type (Task works well) and use the smart values below in the summary and description. Name the rule, turn it on.

  3. 3. Add the webhook in AppForShare

    Dashboard, Integrations, Add webhook, type Generic. As the URL paste the Jira webhook URL, then a slash, then the secret: https://api-private.atlassian.com/automation/webhooks/.../SECRET. Jira reads the secret from the URL because AppForShare does not send custom headers. Pick build.ready and, if you like, one project.

  4. 4. Test it

    Upload a build. Within a minute a work item appears with the version and the install link. The Send test button sends a ping with no build, so add the condition below if you do not want an empty work item from it.

Work item for each new build

Summary:
Test {{webhookData.data.build.name}} {{webhookData.data.build.version}} ({{webhookData.data.build.versionCode}}) on {{webhookData.data.build.platform}}

Description:
Install: {{webhookData.data.build.installUrl}}
Bundle id: {{webhookData.data.build.bundleId}}
Release notes:
{{webhookData.data.build.releaseNotes}}

Skip the test ping

Add this condition right after the trigger.

Condition: Advanced compare
First value:  {{webhookData.event}}
Condition:    equals
Second value: build.ready

Bug when a store rejects a release

A second rule with its own webhook, event store.status, needs a connected App Store Connect or Google Play account.

Condition: Advanced compare
First value:  {{webhookData.data.status.tone}}
Condition:    equals
Second value: bad

Summary:
{{webhookData.data.status.store}}: {{webhookData.data.status.app}} {{webhookData.data.status.title}}

Description:
State: {{webhookData.data.status.state}}
Bundle id: {{webhookData.data.status.bundleId}}

Questions

Which plan do I need?
Webhooks are part of Pro and Team. On the Jira side Automation is included in every Jira Cloud plan, with a monthly run limit that depends on the plan; each delivery that starts the rule counts as one run.
Do I need to install an AppForShare app in Jira?
No. This uses Jira Automation, which is built in. A listed AppForShare app on the Atlassian Marketplace is on the way; this rule keeps working after it ships.
Nothing shows up. What should I check?
Open the rule audit log in Jira. "Unauthorized" means the secret is missing from the end of the URL. If the log is empty, check the webhook in AppForShare: its last status and error are shown under Integrations.
Can I comment on an existing work item instead?
Yes. Put the work item key in the release notes, for example "Fixes APP-142". In the rule, add a Lookup work items action with the JQL key = {{webhookData.data.build.releaseNotes.match("([A-Z][A-Z0-9]+-\d+)")}} and then Comment on work item for the looked up items.

Every event and field is listed on Webhooks. Using Teams? See Microsoft Teams.