Argo CD ListenerDeployment tracking · for Jira

Every Argo CD deployment, on the Jira issue it shipped.

Argo CD Listener publishes each deployment to the Jira issues it contains, with the environment, version and status. Product managers, testers and support see what reached production without asking the team or opening Argo CD. It is made for teams that deploy to Kubernetes with Argo CD, and it reports deployments only.

Push only No code cloning AES-256 encrypted
Argo CD Listener links each Argo CD deployment to its Jira issues, using your repositories on GitHub, GitLab, Azure DevOps or AWS CodeCommit
Connects Argo CD Jira Cloud Reads from GitHub GitLab Azure DevOps AWS CodeCommit
On the issue

See where every issue is deployed

Each Jira issue lists the environments it has reached, with the version, status and time of every deployment and a link back to Argo CD. Nobody has to ask whether a fix is in production.

  • Shown in Jira's own Deployments section
  • Production, staging, testing and development told apart
  • One deployment can link to many issues
Argo CD deployments to production, staging and development shown on a Jira issue
One log

Track every deployment in one place

The Deployments tab lists the last 30 days of deployments across all your applications, each with its environment, version and linked issues. Filter by result to find the ones that did not reach Jira, and why.

  • Linked, waiting, failed and paused deployments at a glance
  • A reason beside deployments that did not reach Jira
  • Search by application, version or Jira issue key
The Deployments tab of Argo CD Listener, listing recent deployments with their application, environment, version, Jira issue keys and result
How it fits your setup

Built around the way you already deploy

Push only

Argo CD sends a webhook after each successful sync. Argo CD Listener never calls Argo CD, so it can stay on a private network.

Linking that matches your process

Jira issue keys in GitOps commits, a version in Chart.yaml or a values file, an image tag or an Application annotation.

The whole release

Reads every commit since the previous deployment, so each issue that shipped is linked, not only the last one.

Environments mapped for you

Environment rules turn application names, paths and namespaces into Jira's production, staging, testing and development.

Guided setup

A four-step wizard generates the Argo CD notifications config and imports your applications from their manifests.

You choose what is published

Turn publishing on or off per application, or pause it for the whole site without losing your setup.

Nothing reaches into your cluster

Argo CD Listener only receives the events Argo CD sends, and reads what it needs from Git to find the Jira issues behind a deployment.

Read our security overview
Outbound onlyArgo CD needs outbound HTTPS and nothing else. No inbound access, no Argo CD token, no agent in the cluster.
We never clone your repositoriesCommit messages, tags, your Application manifests and the version file you name are read through provider APIs. Your application source is not.
Encrypted in transit and at restTLS everywhere, AES-256 at rest, and access tokens you control.
FAQ

Questions, answered

Does Argo CD have to be reachable from the internet? +

No. Argo CD's notifications controller sends each event to Argo CD Listener over outbound HTTPS. Argo CD Listener never connects to Argo CD, so your instance can stay on a private network.

Does it show commits, branches and pull requests? +

No. Argo CD Listener adds deployments to Jira issues and nothing else. It reads your Git repositories only to find which issues a deployment contains. To see commits, branches and pull requests on your issues, use one of our Git Listener plugins. A repository can be connected to one of the two at a time.

How does a deployment get linked to Jira issues? +

You choose how during setup. Argo CD Listener can read Jira issue keys from the GitOps commit that Argo CD synced, or read a version from Chart.yaml, a values file, the image tag or an Application annotation and look it up as a Git tag or commit in the application's repository. It then collects the Jira issue keys from the commits in that release.

Which Git providers are supported? +

GitHub, GitLab, Azure DevOps and AWS CodeCommit, for both GitOps repositories and application repositories. On AWS CodeCommit only the deployed commit is inspected for Jira issue keys, because CodeCommit cannot list the commits between two deployments.

What do I have to change in Argo CD? +

One thing: merge the notifications config that setup generates into the argocd-notifications-cm ConfigMap. It adds a webhook, a message template, a trigger and a subscription. Nothing is installed in the cluster.

Do you clone or store my source code? +

No. Argo CD Listener reads commit messages, tags, your Argo CD Application manifests and the version file you name (for example Chart.yaml) through each provider's API. Repositories are never cloned, and your application source is not read.

Does it work with ApplicationSets and multi-source applications? +

Yes. An application with several sources is handled like one with a single source. Applications generated by an ApplicationSet have no manifest to import, so they are added when they first deploy.

How do I get it? +

Argo CD Listener is a Jira Cloud app sold through the Atlassian Marketplace and billed by Atlassian, with a free trial. Contact us if you would like to hear when it is listed or have a question about your setup.

Also from Mage Software

Looking for Git activity on your issues instead?

Know what shipped, where and when

Connect Argo CD to Jira with one webhook and a four-step setup.