-
Suggestion
-
Resolution: Won't Fix
Summary
The domain verification status is MISSING_TOKEN and when the users try to verify the domain again it shows the following message:
Which does not have any link to the status MISSING_TOKEN that is usually triggered when there is an issue to maintain/confirm the domain claim.
Steps to Reproduce
Unknown
Expected Results
Either that error should not be displayed or the status of the domain verification should be different.
Solution / Workaround
No current workaround but disregard the error message and verify the domain.
[AX-380] *MISSING_TOKEN* status leading to a incorrect "Domain already verified" error
Component/s | Original: Domain Claim - Initial Setup [ 53302 ] | |
Component/s | New: Domain Verification - Initial Setup [ 80145 ] | |
Key |
Original:
|
New:
|
Support reference count | Original: 10 | |
Project | Original: Atlassian Guard [ 18910 ] | New: Admin Experience [ 24210 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | New: timeout-suggestion-bulk-close |
Remote Link | New: This issue links to "Page (Confluence)" [ 480551 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 473684 ] |
Workflow | Original: JAC Bug Workflow v3 [ 3332417 ] | New: JAC Suggestion Workflow 3 [ 3757073 ] |
Issue Type | Original: Bug [ 1 ] | New: Suggestion [ 10000 ] |
Priority | Original: Medium [ 3 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Interest [ 11772 ] |
Support reference count | Original: 9 | New: 10 |
Support reference count | Original: 8 | New: 9 |
Priority | Original: Low [ 4 ] | New: Medium [ 3 ] |
Support reference count | Original: 7 | New: 8 |