Not getting publish notifications sent to Jira

[sfmartinw]

We are frequently asked by QA whether a given PR has been deployed yet and if it’s ready for testing. Our OPS teams have the same question. To alleviate that, we followed the instructions here:
https://shiranuisoftware.com/products/ndjc/
This seems to work, and our Jira tickets get a checkbox next to the environments a PR was deployed to. See this example:

Unfortunately, this updates when a PR is deployed but not when it’s published. Turns out nobody cares that a PR is deployed. Everyone cares whether it’s published.

How do we shore the publish notification in Jira instead of the deployment notification?

[katrina-r]

Hey @sfmartinw,

You should be able to use webhooks + our deploy notifications to get successful deploys notifications into Jira. Create your webhook in Jira (see the link below for more information). Go to Site Settings > Build & Deploy > Deploy Notifications. Select “add notifications” from the drop down and set up the webhook you created in Jira. Save these settings

More information

Jira Docs | Webhooks - https://developer.atlassian.com/server/jira/platform/webhooks/
Netlify Docs | Deploy Notifications & Outgoing Webhooks - Deploy notifications | Netlify Docs

[sfmartinw]

Thanks for the help. I have that configured as you described, but I have two problems.

1. Our QA and Operations team wants to know when a feature is live. Given that it could be days between a PR being deployed and published, we really need PUBLISH notifications.

2. Even with the existing Deployment Notifications, we’re seeing multiple notifications sent to Jira. We tried sending a notification only when “when deploy starts” or only when “when deploy succeeded”, but we find that PRs send either 1 or 2 signals back to Jira. I don’t understand why two are generated or what we can do to get just ONE. I wonder if the intrucftions published on “Netlify Deploy for Jira” are incorrect.

-Martin

[katrina-r]

So the following are the only event notifications available at this time:

Manage deploys

The docs you provided seem to be for a third party app for Jira. They do utilize the “deploy succeeded” notification to indicate to Jira that the deploy was published. However I noticed that their docs also recommend to include relevant issue keys:.

Step 4: Include the relevant Jira issue keys in the branch name or commit message.

You may want to reach out to the “Netlify Deploy for Jira” app developer for clarification. They should be able to provide further support, as this is a third party app. You can view their support contact information here: Netlify Deploy for Jira | Atlassian Marketplace

Another option would be to lock deploys until you would like to publish the site: Manage deploys | Netlify Docs

[sfmartinw]

Hi,
Gotcha. I checked with the developer of “Netlify Deploy for Jira,” who confirmed that they could not get a publish notification because Netlify never implemented that feature.

Does that put the ball back in your court regarding how we get a notification when a build is published? Was there a reason why this functionality was omitted? Is any notification of publishing on the roadmap?

Thanks,
-Martin

[audrey]

Hi @sfmartinw ,

Thanks for the feedback! We do have a feature request filed for this. I can’t say when or if the feature will be released or a time frame for when it may be available. However, I’ve added your voice to the feature request and if it is released, we’ll notify you.

[bigwoof91]

For what it’s worth, my team really needs this feature too. We have auto-publishing turned off for our production sites, and we only care when our builds are indeed Published.

Since we can’t receive notifcations, this is a manual process of pinging the team to let them know—this is a real drag in our release process / operations / daily routine.

[SamO]

Hi @bigwoof91 welcome back to the forums! Thank you for letting us know how this feature is affecting your team. I appreciate it and I hear your concerns. I hope we will have an update from the team soon.