-
Suggestion
-
Resolution: Won't Fix
-
10
-
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.
[ACCESS-629] *MISSING_TOKEN* status leading to a incorrect "Domain already verified" error
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Labels | New: timeout-suggestion-bulk-close |
This keeps happening for some reason. I have to log in and click verify domain to fix it and stop the email warnings.
Thank you for your valuable input and comments. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish.
This suggestion is a priority for our development team, but I am not able to provide an accurate estimate for when this will be resolved. We will update this issue as soon as we can confidently project a release.
Please don't hesitate to contact me if you have any questions.
Regards,
Avni Barman
Email
Product Manager, Atlassian Access
| 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 |
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!