Thus, in the end, fixed and resolved mean exactly the same.
Not always. Depends on the company's philosophy. I worked in many I/T departments where fix means, "we just put something in place" (work around, disabled features, zap rtn to convert ongoing bad data to proper format [rather than fixing the cause of the bad data to begin with], etc) until we can get it resolved.
Fix could mean temporary solution (although not always the best solution - just enough to slow down or stop the issue from occuring / being reported). therefore it is still in open issue.
Resolved could mean they got to the core of the issue, and provided a permanate solution so that it never occurs again. Therefore the issue is closed.
The end user thinks fixed and resolved are the same, but to a programmer / engineer; fixed means off my plate for now while I work on something else, or work on getting it resolved.
Like a resturant, what goes on in the kitchen; sometimes you do not want to know.
I once worked for a major Medical laboratory testing company. their whole philosophy was providing fixes and work arounds, they never resolved anything - drove me nuts. talk about your spaghetti code to support:
Input from user -> routine to correct the data to the correct format -> routine to correct a problem that the last routine caused -> filer -> post-filer to convert the data to the outdated filing structure -> pre-display to convert data to new display structure -> routine to fix problem in pre-display -> routine to format data into obsolete fields -> Display to user.