Stale links to topics migrated to Adobe domains

[Tomasito665]

Summary (*)

Adobe migrated Magento documentation to Adobe domains.
https://devdocs.magento.com/migrated.html

Examples (*)

The pull request description template itself is a clear example:

Please provide [Severity](https://devdocs.magento.com/guides/v2.4/contributor-guide/contributing.html#backlog) assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

The link points to https://devdocs.magento.com/guides/v2.4/contributor-guide/contributing.html#backlog, which was moved to https://developer.adobe.com/commerce/contributor/guides/code-contributions/#community-backlog-priority.

Proposed solution

The solution is simple enough: update the links :-)

---

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 with no 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”.

[m2-assistant]

Hi @Tomasito665. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[sdzhepa]

Hello @Tomasito665

Could you please be more specific or provide more details about where exact wrong links?
In the description, you provided an example for the pull request but PR template does not have a section for Severity

Template in use: https://github.com/magento/magento2/blob/2.4-develop/.github/PULL_REQUEST_TEMPLATE.md

For issues, all templates can be found https://github.com/magento/magento2/tree/2.4-develop/.github/ISSUE_TEMPLATE

1. bug_report.yaml - has correct(updated) link for severity bug_report.yaml#L65
2. developer-experience-issue.md has wrong link developer-experience-issue.md#L23 BUT it is fixed in this PR Convert GitHub issue templates to issue forms #35990
3. feature_request.md - does not have this section for Severity
4. story.md - does not have this section for Severity

Noteі:

• old links could be only in the old issues(that were created/reported before changes). I think(imho) the effort and time required to update all old issues does not worth the result
• all newly reported issues should have correct links

[Tomasito665]

Hello @sdzhepa,

Thanks for coming back to me. If you click New issue → Developer experience issue, the template still contains the old links. Many links on other documentation are also old, including some links on the main README. A few examples:

• https://github.com/magento/magento2/blob/2.4-develop/.github/ISSUE_TEMPLATE/developer-experience-issue.md?plain=1#L23
• https://github.com/magento/magento2/blob/2.4-develop/README.md?plain=1#L18-L21
• https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/QuoteGraphQl/README.md?plain=1#L28
• https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Email/README.md?plain=1#L37-L40

For more examples, search for https://docs.magento.com in this repository:
https://github.com/magento/magento2/search?q=https%3A%2F%2Fdocs.magento.com

old links could be only in the old issues(that were created/reported before changes). I think(imho) the effort and time required to update all old issues does not worth the result

I agree.

[m2-assistant]

Hi @engcom-November. 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 label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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.

[engcom-November]

Hi @Tomasito665 ,
Thank you for reporting and collaboration. I believe updates/modifications to devdocs should be reported in this repository. Hence raised new issue report for the same: magento/devdocs#9523 . Kindly check and move on this issue for latest updates / solutions on the same.
Thank you.

[Tomasito665]

Hi @engcom-November,

I filed a pull request to update all links to migrated documentation to their updated URLs. It has been two days since I filed the PR and yet CI checks appear in progress still. How long do they normally take? Am I missing something?

Thanks

[engcom-November]

Hi @Tomasito665 ,
Thank you for the response. The issue raised by me in devdocs repository has been closed.
Reason: They are currently working on updating the navigation on the devdocs home page to point to new locations and will not implement redirects on devdocs until they finish migrating all content. Kindly check this https://community.magento.com/t5/News-Announcements/Community-Monthly-Update-February-2022/td-p/492851#toc-hId-828475519 for more information.
Thank you.

[Tomasito665]

Hi @engcom-November,

Thanks for your response. The issue you describe is about building in redirects from the old to the new URLs in the Magento docs repo, which is related but different than the issue described in this issue. In this issue, I refer to the URLs in this repository, magento2, which point to the old URLs. The pull request I opened updates all links to their new locations, removing the need to redirect at all. Because of that, I would like to reopen the issue until the pull request is closed. Could you do that?

Thank you!