Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to send deployment info from Jenkins when no changes have been made?

We are using Jenkins (scripted pipelines) and are so excited to be leveraging the new Deployments view in Jira! We ran into one issue when running manual deployments (sans changelog).

Our current workflow is that dev / qa are deployed from the same branch, and dev shows up in the deplyoment view, but QA does not because Jenkins' changlog service does not pull in the changes since its been previously deployed.

  1.  Is there a plan to integrate a parameter into jiraSendDeployment which would allow us to include the issue key there?
  2. We are also looking into manually writing a changelog.xml file for the build, but wanted to ask if that was the right approach? 



1 answer

0 votes
Dario B Atlassian Team Feb 16, 2021

Hello @Vanessa Anderson ,

I don't have a wide knowledge on this topic so please excuse me if I write anything wrong.

However, I have asked our dev team and I have been told that deployments from the same branch in different environments should pop up in the issue view as long as you configure the jiraSendDeploymentInfo in each stage. Each environment in your pipeline should be a different stage. You can find some examples in the below documentation pages:

pipeline {
     agent any
     stages {
         stage('Deploy - Staging') {
             when {
                 branch 'master'
             steps {
                 echo 'Deploying to Staging from master...'
             post {
                 always {
                     jiraSendDeploymentInfo site: '', environmentId: 'us-stg-1', environmentName: 'us-stg-1', environmentType: 'staging'
         stage('Deploy - Production') {
            when {
                branch 'master'
            steps {
                echo 'Deploying to Production from master...'
            post {
                always {
                    jiraSendDeploymentInfo site: '', environmentId: 'us-prod-1', environmentName: 'us-prod-1', environmentType: 'production'



Also, regarding providing the issue keys to the pipeline, I believe that this is documented in: Integrate Jira Cloud with Jenkins

Specify custom logic to get issue keys

By default, the plugin extracts issue keys from all the commit messages in the change log of the build. It is possible to override this behavior to add your own logic and supply the list issue keys as an issueKeys parameter.

jiraSendDeploymentInfo site: '<sitename>', 
environmentId: 'us-prod1', environmentName: 'us-prod2', 
environmentType: 'production', issueKeys: ['DEV-001', 'DEV-002']


For more details on this topic, you may want to review below links:




Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,193 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you