Fixed - CHANGELOG.md is reporting the incorrect issue links

[ansari-ziyaurrahman]

Fixed - CHANGELOG.md is reporting the incorrect issue links #27049

Description (*)

Fixed - CHANGELOG.md is reporting the incorrect issue links #27049

Fixed Issues (if relevant)

1. CHANGELOG.md is reporting the incorrect issue links (I expect to see this in the changelog) #27049: Fixed - CHANGELOG.md is reporting the incorrect issue links CHANGELOG.md is reporting the incorrect issue links (I expect to see this in the changelog) #27049

Manual testing scenarios (*)

1. check 2.3.4 changelog for Fatal error: Class 'Mage' not found #167 it redirect to wrong Issue

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[m2-assistant]

Hi @ansari-krish. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

[lbajsarowicz]

@magento run all tests

[hostep]

@ansari-krish: this one line fix is not enough, there are a bunch more incorrect lines:

#773 -- problem jquery (fixed in magento/graphql-ce#797)
#271 -- Check Data should validate gallery information (fixed in magento/graphql-ce#489)
#815 -- Installation is incomplete. Check the console log for errors before trying again. (Windows 7 WAMP) (fixed in magento/graphql-ce#842)
...

We should also try to figure out how this file gets generated, I'm assuming some kind of script is used for this but I'm not sure if it will be in this repository, if a script is being used, the correct fix here would be to fix the script and then generate that file again.

@lbajsarowicz: do you happen to know more about this? Or do you know somebody inside Magento who can help explain this further? @sdzhepa maybe?

[lbajsarowicz]

@hostep That's actually good point from your side.
Let me call @VladimirZaets - maybe he'll be able to provide the solution.

[engcom-Alfa]

@magento run all tests

[engcom-Alfa]

QA not applicable

[lenaorobei]

@ansari-krish CHANGELOG.md is being generated by our internal tools.
I created a task to address this issue. Unfortunately 2.3.x release line is not publicly available so I need to close this PR. We will fix it internally taking all wrong links into account.

[m2-assistant]

Hi @ansari-krish, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.