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

Ticket deployments view only shows the latest deployment


We are currently submitting our builds and deployments information from Jenkins to the JIRA Cloud instance via the corresponding API. 

In the documentation it states that 


Deployments are identified by the combination of pipelineIdenvironmentId and deploymentSequenceNumber

In our case, for each deployment in the same environment pipelineId and environmentId stay the same and the deploymentSequenceNumber is an incremental int(Jenkins build number). However the ticket deployments panel does not show multiple deployments separately and only shows the latest one, which gets updated (new name, new modified time).

The general Deployments panel shows the history of all deployments correcly.

I can't find any information if this is by design or am i doing something wrong in submitted metadata?

I would expect the ticket view to show all the deployments (albeit on the same environment and the same pipeline) to be shown.

Can you shed some light on this for me please? 



1 answer

1 accepted

0 votes
Answer accepted
Dario B Atlassian Team Mar 23, 2021

Hello @Evgenios Soroka ,

Before going any further, can you kindly let us know whether you are using the open source integration with Jenkins built by Atlassian (links below) or if you are using a custom integration you have built yourself?




Hi @Dario B ,

We are using a custom integration and submitting the data via the Deployments API

Dario B Atlassian Team Mar 24, 2021

Thanks for your quick reply @Evgenios Soroka !

I have contacted the dev team responsible for this and I been told that your understanding is correct:

  • deploymentSequenceNumber makes a deployment unique in the timeline of a pipelineId + environmentId.

  • it's possible to perform an update when the updateSequenceNumber is incremented. 

  • the development panel always presents the latest deployment (latest deploymentSequenceNumber) of a single pipelineId + environmentId. This is because the most important information for the end user is to know which is the state of the latest deployment, as we do for builds as well.

Kindly let me know if this helps or if you have further questions on this topic.



Like Evgenios Soroka likes this

Hi @Dario B ,

Thank you for your response, yes that clarifies it perfectly!

Like Dario B likes this
Dario B Atlassian Team Mar 26, 2021

You are very welcome @Evgenios Soroka , have a nice weekend! 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Bitbucket Smart Commits vs. Genius Commits - What's the difference?

If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...

106 views 0 2
Read article

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