Redmine

+1 It would be nice to have a permission for this so only specific Roles can edit the reporter.

To prevent abuse, and to keep track of "who did what?", user entering the issue have to be visible, too.
Personnaly, I see this as a plugin (only big companies can have usage of that) :)

1. Issue "author" (should perhaps be "recorder" or something) is a separate role from the actual issue source, so both should be stored. That would get this sorted.

2. Also, traceability would be OK, if changing the sender will get logged. (Changing other fields are logged already anyway).

3. Coordinators should definitely be able to do this "on behalf" submission. It's pretty awkward now having to add them as watchers, especially, because they are often not project members at all (so you first have to add them, polluting the participant lists, just for letting them be watchers).

So, please, please, don't "outsource" this core function to a plugin.

Thanks!

See also: #1739

I would welcome both of these issues.

+1 This would be nice for us too

+1

If I get a phone call, walk-up, or direct email, I would like to record the ticket "on behalf of" the author and make myself the assigned-to person. Using watchers will keep everyone in the loop on updates, but will not be properly reflected in the reports (ie, how may issues has person x reported).

I'd suggest making the author modifiable, like the assigned-to, in the "more" section with the ticket title and initial description.

+1

+1 I too think this is important and hope this will be added to the 1.0 Release.

• The creator of the issue should be immutable.
• The solid approach is to make use of the custom fields.
  The problem with the custom fields approach is that it is missing the data types (Format) needed, namely, "User".

"User" would produce a custom field of the same type and behavior as "Assigned To".

+1 we do this all the time. We field e-mails from customers who don't feel like using redmine and enter their request in directly.

+1 I often get emails from staff who forget to use the dedicated tracker email and I need to enter their issue into the system and assign them as the ticket owner.

+1

+1

+1

+1 A user/owner field would be nice, so it would behave like if the person created the issue itself, but the "added by" would be someone else.

+1 The creator (original reporter) of an issue, like any other reporter, should not be changeable.

On the other hand, the owner of an issue, i.e. the person that

• monitors the issue;
• acts as the opponent to the Assignee;
• receives notifications about every update of the issue, without being explicitly listed as a Watcher;
• may be granted "own issue" privileges, e.g. "Edit own issues" or "Set own issue public/private";
• may have assigned the special issue visibility "Issues created (i.e. owned) by or assigned to"; and
• may have granted special workflow privileges listed under "Additional transitions allowed when the user is the author (i.e. owner)"

must be changeable. Just like the Assignee.

The difference is default Assignee = none, but default Owner = Creator.

+1 Great feature

+1 Please implement this, we really need to be able to stop emails going to person who created the issue, we have few people who changed their work position and should not get this communication any more. Also it would be great if author could click on unwatch to stop this communication. Even the project wide option which will disable sending any communication to the author could help.

+1, would be VERY usefull, please implement it like described in note-16

Duong Tran wrote:

+1 The creator (original reporter) of an issue, like any other reporter, should not be changeable.

On the other hand, the owner of an issue, i.e. the person that

• monitors the issue;
• acts as the opponent to the Assignee;
• receives notifications about every update of the issue, without being explicitly listed as a Watcher;
• may be granted "own issue" privileges, e.g. "Edit own issues" or "Set own issue public/private";
• may have assigned the special issue visibility "Issues created (i.e. owned) by or assigned to"; and
• may have granted special workflow privileges listed under "Additional transitions allowed when the user is the author (i.e. owner)"

must be changeable. Just like the Assignee.

The difference is default Assignee = none, but default Owner = Creator.

+1