magento2: Magento 2.4.0 release notification not showing up in backend
Preconditions (*)
- Magento 2.4.0 or 2.4.1 or 2.4.2 or 2.4.3 or 2.4.4 or 2.4.5
Steps to reproduce (*)
- Setup clean 2.4.0 or 2.4.1 or 2.4.2, … installation, not a
2.4-develop
instance! (see reasoning below) - Login to backend (struggle your way through the whole 2FA process rigmarole)
- Once finally logged in, seeing a notification at the bottom of the page:
We’ll try to show it again the next time you sign in to Magento Admin.
To learn more about new features, see our latest Release Notes in DevDocs' Release Information
- Also notice the strange ‘Next >’ link in the footer
- Logout in backend
- Login to backend
- Not seeing any release notifications popup
Expected result (*)
- Not being confused: if there are release notes for 2.4.0, show them, if there aren’t, don’t show that
We’ll try to show it again ...
message
Actual result (*)
- Being confused: is there a release notes popup for Magento 2.4.0? If yes, why isn’t it showing up? If no, why is that message
We’ll try to show it again ...
showing up …
Additional information
https://github.com/magento/magento2/issues/29363#issuecomment-754913283
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 16 (11 by maintainers)
✅ Confirmed by @engcom-Oscar Thank you for verifying the issue. Based on the provided information internal tickets
MC-41875
were createdIssue Available: @engcom-Oscar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.