It would help a lot if the fix(es), either in the form of Perforce changelists and/or GitHub commits, were added to the UE issue page whenever the issue is marked as fixed. This would greatly facilitate cherry picking changes when one is trying to fix an engine bug.
Fix CLs are actually something that should populate automatically for most issues. In cases where there isn’t one, it’s most likely because it might not have been filled in on the internal JIRA ticket (there are several different CL fields in our internal tickets so it might have been a different field that doesn’t have a public counterpart) or is from a different stream that isn’t publicly accessible.
GitHub commits are a bit more complex since our internal tickets don’t have any direct mappings to the GitHub commit for a fix. We used to have an automation that pulled the GitHub commit, but a series of changes to the way things worked caused it to stop working. We’d need to rebuild this, which is something I’d like to revisit, but haven’t had the opportunity to do so yet.
That said, if you notice any Issues marked as Fixed that don’t have a Fix CL or you need help getting to the GitHub commit, feel free to ask, either in the linked EPS question, or by creating a new question referencing the issue and we should be able to help.
Thank you Raghib. Good to know that usually the info will be there.
Whenever Github implements the ability to search commits per branch, it will be a lot easier to find the commits on there. For now, fetching the repro locally works as well, or as you said just posting a question.