For Work Needed cases, there should be����a description of the problem sufficient for you the reproduce it.�� If not, ask for one. ��
Try to locate which build version introduced the bug.�� I use PharoLauncher to help download and manage a large number of Image versions while manually bisecting versions like git bisect.�� Once determined, check the build announcements on pharo-dev for which slices were loaded to go from good image version to bad image version.
For Resolved cases, there should be a description of the problem sufficient for you the reproduce it, then apply the fix and repeat the actions to confirm its fixed. If not, ask for one.
I find I learn a lot by reviewing the fixes of others.�� I tend to do <Changes> first, then leave that open while I do a <Merge>.�� This makes it easier to go the the changed methods and scatter a few 'self halt's so that I can trace the running code.�� Sometimes in a separate Image I put the same 'self halt's in the original methods and step through both new and old simultaneously.
cheers -ben