Magento_Analytics wrong link
Closed this issue · 9 comments
Preconditions (*)
- I'm using Magento 2.3.3
Steps to reproduce (*)
- Access the admin panel
- Click in this link circled in the image below.
Expected result (*)
- In my opinion, it should go to the login page
- Or to the Advanced Reporting page.
Actual result (*)
- The button is redirecting to this page below.
Additional Information
I created this PR to check if the Magento BI token is configured, if it's configured and not synchronized, it will redirect to the same page, if it's not configured it will redirect to the doc page.
Hi @rafaelstz. Thank you for your report.
To help us process this issue please make sure that you provided the following information:
- Summary of the issue
- Information on your environment
- Steps to reproduce
- Expected and actual results
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.3-develop instance
- upcoming 2.3.x release
For more details, please, review the Magento Contributor Assistant documentation.
@rafaelstz do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
- yes
- no
- Join Magento Community Engineering Slack and ask your questions in #github channel.
Hi @itsPranith. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇
-
1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the labelIssue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until labelIssue: Format is valid
appears. -
2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add
Issue: Clear Description
label to the issue by yourself. -
3. Add
Component: XXXXX
label(s) to the ticket, indicating the components it may be related to. -
4. Verify that the issue is reproducible on
2.3-develop
branchDetails
- Add the comment@magento give me 2.3-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on2.3-develop
branch, please, add the labelReproduced on 2.3.x
.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here! -
5. Add label
Issue: Confirmed
once verification is complete. -
6. Make sure that automatic system confirms that report has been added to the backlog.
@magento give me 2.3-develop instance
Hi @itsPranith. Thank you for your request. I'm working on Magento 2.3-develop instance for you
Hi @itsPranith, here is your Magento instance.
Admin access: https://i-25411-2-3-develop.instances.magento-community.engineering/admin
Login: admin
Password: 123123q
Instance will be terminated in up to 3 hours.
Hello @rafaelstz and @itsPranith
It looks like very similar to this #24180
Previously issue was closed as cannot reproduce because after enabling Adv. Reporting needs some time for initial synchronization. It mentioned in DevDoc, the last point of Step 1: Enable Advanced Reporting
For more details please see this #24180 (comment)
Could you please confirm that you have the same issue and after synchronization, it works as expected?
Hi @sdzhepa,
It's not the same issue because today it's not considering if the Magento BI token is configured, even if it's not synchronized yet.
I created this PR to check if the Magento BI token is configured, if it's configured and not synchronized, it will redirect to the same page, if it's not configured it will redirect to the doc page.
✅ Confirmed by @sdzhepa
Thank you for verifying the issue. Based on the provided information internal tickets MC-22634
were created
Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
Hi @rafaelstz. Thank you for your report.
The issue has been fixed in #25412 by @rafaelstz in 2.4-develop branch
Related commit(s):
- 9efef990accdc4b2fc094fe3bb68fde3cc178604
- c01dd2a41a4862366148f9a486e402ebed6b0b27
- 6a0f133b6ba40a87321324151910bf44ba8e6811
- d69bd9d9a916f9c3a13793fd1a01bbe77257c7e4
- 42eb8a04a783bdebf692805836beb8db87667bfa
- 1e8b12e4a3e1fe881a56108c97131b17a5c0d6be
- 08c9f33f0c56df5fb12634a2a452f94aeeee0187
The fix will be available with the upcoming 2.4.2 release.