-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
9.12.0, 9.4.11, 9.4.14, 9.12.2, 9.12.7, 9.15.2, 9.17.3, 9.17.4
-
9.04
-
39
-
Severity 3 - Minor
-
83
-
Issue Summary
This is reproducible on Data Center: YES
Steps to Reproduce
- Git Client - create organisation including 2 repositories
- In git archive one of repositories
- Link organisation to Jira via DVCS Connector plugin
- 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.
- Ensure in the view of DVCS Accounts organisation has FAILED webhook status.
- Go to the list of repositories within that account and UNLINK repository marked as FAILED
- 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
- duplicates
-
JSWSERVER-25447 DVCS Webhook status should ignore deleted or unlinked repositories
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
FLASH-4095 Loading...
DVCS presents wrong webhook migration status for linked account/organisation
-
Bug
-
Resolution: Fixed
-
Medium
-
9.12.0, 9.4.11, 9.4.14, 9.12.2, 9.12.7, 9.15.2, 9.17.3, 9.17.4
-
9.04
-
39
-
Severity 3 - Minor
-
83
-
Issue Summary
This is reproducible on Data Center: YES
Steps to Reproduce
- Git Client - create organisation including 2 repositories
- In git archive one of repositories
- Link organisation to Jira via DVCS Connector plugin
- 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.
- Ensure in the view of DVCS Accounts organisation has FAILED webhook status.
- Go to the list of repositories within that account and UNLINK repository marked as FAILED
- 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
- duplicates
-
JSWSERVER-25447 DVCS Webhook status should ignore deleted or unlinked repositories
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
FLASH-4095 Loading...