Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-89992

Add ability to map environment type of unmapped GitHub deploys

XMLWordPrintable

    • 1
    • 7

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, GitHub integration performs a text match to map environments from deploys where the text matches are:

      • Developemnt: development, dev, trunk
      • Testing: testing, test, tests, tst, integration, integ, intg, int, acceptance, accept, acpt, qa, qc, control, quality
      • Staging: staging, stage, stg, preprod, model, internal
      • Production: production, prod, prd, live
      • Unmapped: no matches

      It would be a good idea to have some way to map environments that were not matched and are currently set as unmapped in case the GitHub environment name does no match the predefined texts.

            [JRACLOUD-89992] Add ability to map environment type of unmapped GitHub deploys

            Constantine Genchevsky added a comment -

            This looks like a solution

            Constantine Genchevsky added a comment - This looks like a solution

            doug.bradbury added a comment -

            This is apparently supported now in the github connector:  https://github.com/atlassian/github-for-jira/blob/main/docs/deployments.md

            doug.bradbury added a comment - This is apparently supported now in the github connector:   https://github.com/atlassian/github-for-jira/blob/main/docs/deployments.md

            Constantine Genchevsky added a comment -

            Any updates?

            Constantine Genchevsky added a comment - Any updates?

            Alan added a comment - - edited

            This is being worked on for gitlab integration here: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/80539

            Alan added a comment - - edited This is being worked on for gitlab integration here: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/80539

            bhunt added a comment -

            This is a must for it to work for us. Our staging environments map properly, but our production environments are named purely after the products they represent without extra keywords. This means that they all come through as 'unmapped'.

            E.g.

            Staging: service-staging

            Prod: service

             

            bhunt added a comment - This is a must for it to work for us. Our staging environments map properly, but our production environments are named purely after the products they represent without extra keywords. This means that they all come through as 'unmapped'. E.g. Staging: service-staging Prod: service  

            Alan added a comment - - edited

            Having a similar issue with Gitlab integration where all deployments are unmapped or development. More info: https://community.atlassian.com/t5/Jira-Software-questions/Why-do-all-CI-CD-deployment-types-show-as-development/qaq-p/1939818#U1939890

            Alan added a comment - - edited Having a similar issue with Gitlab integration where all deployments are unmapped or development. More info: https://community.atlassian.com/t5/Jira-Software-questions/Why-do-all-CI-CD-deployment-types-show-as-development/qaq-p/1939818#U1939890

              Unassigned Unassigned
              87999cee8e58 Alexandre Furtado
              Votes:
              64 Vote for this issue
              Watchers:
              34 Start watching this issue

                Created:
                Updated: