Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Surface version number in Github/Jira linked deployments

Tim Kranen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 27, 2023

Hi Jira community,

 

We're running into an issue while using the Github for Jira tools that we're very curious to solve. We've implemented some basic deployments using Github actions, and these deployments get successfully displayed in our Jira tickets (following the documentation described here). 

Surfacing the deployments in our Jira tickets is awesome, but there is one feature that it's missing (or we don't know how to set up properly). We mainly work with native mobile apps, which means our 'deployments' are actually uploads to the App Store and Google Play store. It would be amazing if our QA team could check the deployment to one of these stores and actually see the version and build number of the app that was uploaded, so will always download the correct build from the store. 

Is there a way to add additional information to these deployments that can get surfaced in a Jira ticket? Right now we're only aware of being able to set a custom environment, and we could theoretically abuse this system a bit by appending the version number to the environment name, but I'm curious if there are other/better ways to do this. 

Github deployments do allow for us to add a payload json to be added to the deployment, is there any way to make this payload json data visible in the deployment information screen?

 

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events