I agree the "creator" field should be orderable.

Is the Creator field created as only Navigable by design? If so, why?

I don't understand why this field can't be optionally displayed on the View Issue screen. There is a high degree of value seeing this information near the top of the issue because it tells you who was involved in the initial issue, especially since you can't distinguish between an issue created on the Service Desk portal versus created as a "Raise request on behalf of" option. Instead of seeing this field, you have to scroll down and click on the Activity tab. Yet you can display it on a Dashboard via a field. Shouldn't viewing an issue provide you with all of the fields available for more information?

Hi @Admin, we have the same situation. Please, what is your workaround?
Thank you !

Please make the "creator" field orderable. This is really annoying. In Jira Software we are doing a workaround with custom fields, in Jira Servicedesk the "creator" field is shown in the queues but not in the detail view. Thats very irritating

This field can be displayed on the "Issue Detail View" (on Kanban/Scrum boards), so in my mind, it should be available on the view issue screen as well.

Frequently we want to remember who created the issue, while Reporter is changeable and may be a different user altogether. We should have an option to view it on the issue view screen.

Our main issue is that we want support requests to show up in a user's support portal. Often, users will call in or send emails to staff directly and we create tickets on their behalf and assign them as the Reporter. We want these tickets to show up in their portal so they can keep track of their requests. It also helps when we bill the customer so they don't have to search their emails.

Lastly, we also add other users in the client's organization as Request Participants to all tickets (so their team can have visibility) but when they log in to their support portal, they cannot see the tickets they did not create (despite selecting the option to see 'tickets where I am a participant' and 'tickets created by anyone').

Since we have a number of external Jira users creating issues it is absolutely necessary to have this field useable in a screen. Since then we have to continue using our private customfield "creator" for this purpose. This is a rather un-elegant workaround and so I really like people to vote for the above