[#JRA-7919] Changelog should show issue creator as well as reporter

JIRA

Changelog should show issue creator as well as reporter

Created: 10/Sep/05 03:04 PM Updated: 13/Sep/05 02:49 AM

Component/s:

Backend / Domain Model

Affects Version/s:

3.3

Fix Version/s:

None

Time Tracking:

Not Specified

Participants:	Anton Mazkovoi [Atlassian] and Nick Minutello
Since last comment:	2 years, 51 weeks, 2 days ago
Labels:

Description

« Hide

If the reporter is modified when an issue is raised, there is no record of who actually created the new issue.

Just needs to be shown in the changelog...

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 11/Sep/05 07:12 PM

Hmmm... currently we do not make any change log entries on create.

Would you like the change record to be for the 'reporter' field?

Anton

[ Permlink | « Hide ]

Nick Minutello added a comment - 12/Sep/05 04:28 AM

Not sure I understood the question...

But the changelog should show who the current user was when the issue was created (ie who did the creating as opposed to the reporting)

Does that answer the question?

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 12/Sep/05 07:02 PM

> Does that answer the question?
Sort of

At the moment the 'style' of the change log is:
Field - Old Value - New value

What I am asking is what should be the format for the change log entry in this case? Would you like it to say:
Reporter - Logged in User - The value reporter field has been set to

Cheers.
Anton

[ Permlink | « Hide ]

Nick Minutello added a comment - 12/Sep/05 07:33 PM

Ok, I get you...

Hmm

That pause for thought has left me in two minds.

1) yes make the changelog entry as you described
2) Make "creator" a first-class field of an issue (ie like reporter)

For (2) I can think of a number of instances where this could become handy as/when "creator" is used in permission & notification schemes.

We have quite a few instances where we have dedicated support staff for an application. They help the users out with problems and report bugs.
Now, in 99.768% of the cases, they are raising an issue on behalf of someone else. (NB this is a classic help-desk use-case for Jira)
So the creator AND the reporter are distinct and important in their own right.
That said, you could also achieve the same with a custom user-picker field - but it cant participate in the permission scheme yet - only the notification scheme.

So, perhaps, after all that, the simple answer is (1)

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 13/Sep/05 02:49 AM

Well, this is exactly why we did not want to let users modify reporter

> That said, you could also achieve the same with a custom user-picker field - but it cant participate in the permission scheme yet - only the notification scheme.
This would be the solution I would opt for. That is, for us to create a permission type that is based on a value of the user picker (we already ship a notification type based on user picker).
This will be consistent with us not creating any change logs on issue creation.

Another solution would be to create a read only custom field that populates the remote user during issue creation (and thus records the real reporter).
Not sure if the API can cater for this ATM, but it should be possible.

Final line - I really like ot avoid creating change logs on issue creation.

What do you think?

Anton