Send notification to Jira

The plugin marketplace offers several freestyle steps for your Codefresh pipeline.

One of those steps is the Jira Issue Manager.



This documentation uses the following example. You can either use the example provided to try out the Jira integration or follow along with your own application.

  1. You need an issue in your Jira account that you want to link to your Codefresh pipeline. If you do not have one yet, please create an issue. (Note that the project type and who is creating the issue etc. does not matter.) Alternatively, you can also create an issue first with the Jira step. However, this is not explained in this example.

  2. Next, add the following step to your Codefresh pipeline. In case you are using the example, the codefresh.yml file is already added.

    title: "Add Jira Comment"
    type: "jira-issue-manager:1.0.11"
    stage: "deploy"
      JIRA_BASE_URL: '$'
      JIRA_USERNAME: '$'
      JIRA_API_KEY: '$'
      ACTION: "comment_create"
      COMMENT_BODY: "Build number $ finished in Codefresh"

Let’s look in detail at this step.

  • Everything up to the arguments is similar to other Codefresh steps.

These arguments are required to use the step:

  • JIRA_BASE_URL: This is the url of your organisation e.g. ‘’
  • JIRA_USERNAME: This is usually the e-mail that you are logged in with at Jira
  • JIRA_API_KEY: Note that you will have to create this key. The official Atlassian documentation details how it can be created.

Then we added these arguments for our specific step:

  • JIRA_ISSUE_SOURCE_FIELD: This is the tag that identifies your issue, for example, MKTG-102
  • Within the comment, we use a Codefresh native variable CF_BUILD_URL, which references your pipeline build and allows you to search for your pipeline.

All variables use the Codefresh-specific variable notation ${{MY_VARIABLE_EXAMPLE}}`.

Since it is a new stage in your Codefresh pipeline, you want to add it at the top to your stages, e.g.:

    - "clone"
    - "build"
    - "JiraCommentCreate"

Note that you can provide the variables needed for the Jira step directly in the shared configuration. The benefits are:

  • You do not have to post sensitive information, such as the API key, directly in the codefresh.yml.
  • If you use the same step across multiple pipelines, you don’t have to copy-paste the same variables.

Once you run the pipeline, you should be able to see the following output or similar:

Pipeline with Jira integration

And the comment, including the URL to the pipeline, should be added to your Jira issue:

Comment in Jira

CI pipeline examples
Send notifications to Slack
Create a pipeline