Hi everyone,
We are big fans of the Deployments timeline and its underlying Deployment API provided by Jira Software Cloud:
There are many resources and examples provided by Atlassian here: https://support.atlassian.com/jira-cloud-administration/docs/integrate-your-deployments-with-jira/
We have successfully integrated this api with our Jenkins server that is used for build and continuous integration of our apps: https://support.atlassian.com/jira-cloud-administration/docs/integrate-jenkins-with-jira/
It works really well to give a "ticket centric" view over the past deployments that is especially adapted to CI/CD pipelines.
I think that this topic deserves a dedicated discussion to exchange best practices and real life feedbacks/questions that arise when you start integrating various deployment tools (ex: GitHub, GitLab, Bitbucket, Jenkins,...).
We are quite experienced with Jenkins integration and we will be happy to share this experience with the community.
We would also love to get feedback from other "deployment api" users ! ;-)
You would need to set a Resolution during the transition to the Status verified. Once a Resolution is set it will be displayed.
Note: unresolved is displayed as long no Resolution is set (there is no Resolution "unresolved")
Thanks for quick feedback @Udo Brand! When you say "set a Resolution" - is that just choosing "resolved" from a drop-down? (I'm not admin in our customer JIRA so I can't see the options in the Resolution field/drop down). Just want to be able to provide them with specific instructions ;-).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well there are two ways to achieve this. but both have to be implemented by an admin.
First add a screen with the Resolution field to that transition. Then a user has to choose a Resolution during that transition.
Or second. the Resolution is set via postfunction during that transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.