Field description - Reporter
The Reporter field represents who the end user/reporter of the issue is. In many cases the reporter is also the creator of the issue, but not always.
Default name: Reporter
Terminology variations: None
In-Use: Optional. This field can be set to be used in the issue field configuration.
Mandatory: Optional. This field can be set as mandatory, but need not be.
Data type: A User, which can be an internal or external user, or even a contact.
Access restrictions: (Default) "No access" when created (this field is always set to the issue creator in this case). Editing: "Read/Write" for all internal users, "Read" for external users, and "No access" for support users.
Reporter Company: If this issue field is used, it is always set to the company that the Reporter belongs to.
Project > Settings > General, section "General issue settings":
"Company" and "Reporter" fields should be dependent: This setting makes these fields dependent on each other, so that setting reporter sets the company for example.
Affected by these settings:
Project > Settings > Notifications:
The Reporter of an issue can be set as a recipient of notifications generated by changes to the issue.
General > Settings > Issue configurations > Issue rules.
Reporter can be used in issue rules, either as a criterion, or being set in the rule action.
Reporter tells you who the email/issue/task/request is coming from, even if someone else created the issue for the Reporter.