Deployment / gitlab for Jira Cloud - manual job for deployment does not seemed to be handled

Matthieu Papin
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!
May 6, 2024

Hello there !


I am using the plugin gitlab for Jira Cloud (documentations are here : GitLab for Jira Cloud | Atlassian Marketplace and here : GitLab for Jira Cloud app | GitLab) so that my gitlab information are displayed inside JIRA. Everything works fine as long as the developers refer the JIRA key inside the commits, branches names and the title of the merge requests.

I recently enabled the deployment feature inside JIRA, which is super useful to monitor the deployment done through gitlab (which ticket has been deployment, to which environment, etc.)

Unfortunately, there is one thing that is misleading to me. Indeed, in our pipelines, we have the deployment job for the staging and production environment that are manual jobs (thanks to gitlab: Control how jobs run | GitLab). When these jobs are run, the deployment is displayed inside the deployment tab of the JIRA project. But the deployment is also displayed when these jobs are not. Which leads to a really misleading board. I will post screen shots so that my sentences are a bit more (I hope :)) understandable !


Sans titre (1).png

These deployments have been detected and are marked as "success" inside a non production environment, great :) !


Sans titre.png

Here, you see all the "deployments" in the production environment. However, all these jobs are marked as "unknown" and when looking inside the corresponding pipeline, these jobs have not been run manually by the developer (which is "normal", not every build will lead to a deployment in production).


Is it an issue of the deployment feature ? Is it known ?


Thanks for the help guys.


0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events