We have a gitlab integration with JIRA as per this document. The integration works as many of the features are available, except deployments made to production.
1. When I look into to a project settings -> deployments. I can see all deployments belonging to the Development & Unmapped environment types. None of the deployments are in the Production type.
2. When I look into the project reports -> Deployment Frequency, no deployments show up.
What does JIRA read to know if it's a production deployment ? I'm guessing there's an environment variable or something our custom gitlab pipilene is not using so everything fallbacks to development.
I'm in a team-managed project. Here are some screenshots showing a ticket tied to an MR that's already in production.
Is your Jira project a Team managed project or a Company Managed project?
Can you share with us screen images for what you see in each of these screens?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also I found this Atlassian issue concerning the environment mapping for the Github integration. Maybe the same applies to the integration for Gitlab.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think the issue with the Deployment Frequency report is that it reports on "production" deployments. If none of your environments are recognized as "production" environments then there will be no production deployments on which to report.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agree, that must be the issue. So I think understanding why production deployments aren't mapped as production will unlock this feature. Investigating on resources you provided.
I mistakenly Answered instead of replying :facepalm: with other details.
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.
@Alan +1 also experiencing this issue
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.