Hi @James,

The link says that the issue is fixed ! We really need to identify who is the Creator and who is the current reporter . For the current reporter, everything is fine.
But we loose the Creator when the reporter change

It's important to realise what is happening here - the change history is recorded and will display correctly in the History tab in the view issue page. What is still incorrect is that the ActivityStream code has not been updated to use creator yet and still uses reporter, so the activity and history tabs are inconsistent - fixing the activity streams will fix the issue. You can follow that issue at https://ecosystem.atlassian.net/browse/STRM-2213.

I just installed JIRA 6.3.15 and the above described effect is still present.
This leads to missinterpretation and therefore makes this information useless!

I am still seeing this issue in JIRA 6.2.4.
I created an Issue with Reporter as myself.Call me "B"
It shows in Activity as "B" created an issue.
After 20 mins I edit issue and update reporter to "A"
It shows in Activity as "A" created an issue 20 mins ago
But Activity also shows "B" changed reporter to "A"
But it loses the "B" created an issue message that was originally present.

Something that I think is tripping a lot of people up is that Jira obviously assumes that the Reporter and Creator is the same person. It will present this information under the Activity tab in the issue screen. Changing the reporter will also change the information about who created the issue in the first place. This means we can actually alter the history of an issue!
I shouldn't have to query the database directly to find out who actually created an issue.

a workaround from Answers:
https://answers.atlassian.com/questions/185427/reporter-and-creator-is-different

Not really. When you create an issue, Jira creates it with whatever reporter the user enters. That's it, the first time the issue exists as an entity, it has the reporter on it. If the user changed it from themselves to someone else, you're a bit stuck, because the person doing the typing doesn't actually commit that into the issue.

There's two easy workarounds to prevent the loss of information, but neither will help you for older issues:

1. Use a post-function to set a custom field (I call it "creator") to %Currentuser% on the create transition

2. Remove reporter from the "create issue" screen, so it always logs the current person (and if they need to change it later, leave it on the edit screen)

You can try to work it out from watchers and project activity etc, but that's not always clean enough.

A separate Creator field is definitely necessary for tracking purposes.
And perhaps it should be automatically recorded as current_user, not changeable.
This person should show up in the activity history in first entry as "xxxx created zzz-999".

The reporter field is not always necessary to be filled in, could be empty/NULL.

There is a lack of traceability in Jira since it is not possible to determine who is the creator of the issue.
This is a problem in a CMMI context.
We expect absolutely this feature to be implemented.
Don't forget that a reporter is not always required.
So, a name for creator should always be present without being able to edit it.

We are also interested in being able to see who has created an issue.
Perhaps it is possible to do via a customfield filled out via a Velocity processed Message Custom Field?

Bump I agree this field would be handy. We've had some situations here where some users are assigning issues to other people, but setting the reporter to the same value as the assignee which just confuses the assignee. We've been trying to solve this through education of users, but having the creator logged would be very helpful.