We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-25448

DVCS presents wrong webhook migration status for linked account/organisation

      Issue Summary

      This is reproducible on Data Center: YES

      Steps to Reproduce

      1. Git Client - create organisation including 2 repositories 
      2. In git archive one of repositories
      3. Link organisation to Jira via DVCS Connector plugin
      4. Wait till organisation get linked and DVCS Connector install webhooks remotely (one repository should be marked as SECURED, second one as FAILED). Webhook migration status for particular repository you can check by going to DVCS Accounts -> go to interested organisation to see each repository webhook status.
      5. Ensure in the view of DVCS Accounts organisation has FAILED webhook status.
      6. Go to the list of repositories within that account and UNLINK repository marked as FAILED
      7. Go back to the view of DVCS Accounts

      (After those steps, organisation contains only one SECURED repository)

      Expected Results

      Whole organisation is marked as SECURED

      Actual Results

      Whole organisation is marked as FAILED

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Software Data Center'
            1. Jira Software Data Center
            2. JSWSERVER-25448

            DVCS presents wrong webhook migration status for linked account/organisation

              • Icon: Bug Bug
              • Resolution: Fixed
              • Icon: Medium Medium
              • 9.12.14
              • 9.12.0, 9.4.11, 9.4.14, 9.12.2, 9.12.7, 9.15.2, 9.17.3, 9.17.4
              • DVCS Connector

                Issue Summary

                This is reproducible on Data Center: YES

                Steps to Reproduce

                1. Git Client - create organisation including 2 repositories 
                2. In git archive one of repositories
                3. Link organisation to Jira via DVCS Connector plugin
                4. Wait till organisation get linked and DVCS Connector install webhooks remotely (one repository should be marked as SECURED, second one as FAILED). Webhook migration status for particular repository you can check by going to DVCS Accounts -> go to interested organisation to see each repository webhook status.
                5. Ensure in the view of DVCS Accounts organisation has FAILED webhook status.
                6. Go to the list of repositories within that account and UNLINK repository marked as FAILED
                7. Go back to the view of DVCS Accounts

                (After those steps, organisation contains only one SECURED repository)

                Expected Results

                Whole organisation is marked as SECURED

                Actual Results

                Whole organisation is marked as FAILED

                Workaround

                Currently there is no known workaround for this behavior. A workaround will be added here when available

                        7e8b5dfc9af0 Nitesh Giri
                        1c017edd2c81 awojtasik
                        Votes:
                        15 Vote for this issue
                        Watchers:
                        36 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              7e8b5dfc9af0 Nitesh Giri
                              1c017edd2c81 awojtasik
                              Affected customers:
                              15 This affects my team
                              Watchers:
                              36 Start watching this issue

                                Created:
                                Updated:
                                Resolved: