Requestor field in dashboards

Hi,

is it possible to change the requestor field in dashboards so that it
displays the requestor name instead of the requestor email address?
It would save some horizontal space, allowing more useful information to
be displayed.

I looked a bit into the webinterface, but I didn’t see anything obvious.
Is there a way?

Thanks, Daniel.

Hi,

How users displayed in the UI controlled by config option $UsernameFormat.On Wed, Sep 28, 2011 at 12:59 AM, Daniel De Marco ddm@bartol.udel.edu wrote:

Hi,

is it possible to change the requestor field in dashboards so that it
displays the requestor name instead of the requestor email address?
It would save some horizontal space, allowing more useful information to
be displayed.

I looked a bit into the webinterface, but I didn’t see anything obvious.
Is there a way?

Thanks, Daniel.


RT Training Sessions (http://bestpractical.com/services/training.html)

  • Chicago, IL, USA September 26 & 27, 2011
  • San Francisco, CA, USA October 18 & 19, 2011
  • Washington DC, USA October 31 & November 1, 2011
  • Melbourne VIC, Australia November 28 & 29, 2011
  • Barcelona, Spain November 28 & 29, 2011

Best regards, Ruslan.

Ruslan,

thanks for your answer, however $UsernameFormat seems to only work for
fields like LastUpdatedBy and OwnerName, but not for Requestors.
I still have $UsernameFormat set, by default, to “concise”, but in the
dashboard for the requestor column I get email addresses.

Thanks, Daniel.

thanks for your answer, however $UsernameFormat seems to only work for
fields like LastUpdatedBy and OwnerName, but not for Requestors.
I still have $UsernameFormat set, by default, to “concise”, but in the
dashboard for the requestor column I get email addresses.

Do users for those requestors actually have usernames that aren’t their
email addresses? Check in the admin UI.

Thomas

yes, they do. For example in the dashboard I have both the Requestor and
LastUpdatedBy fields. For the same person I get the full email in the
Requestor field and the username in the LastUpdatedBy field…

Daniel.

  • Thomas Sibley trs@bestpractical.com [09/28/2011 08:38]:> On 09/28/2011 07:58 AM, Daniel De Marco wrote:

thanks for your answer, however $UsernameFormat seems to only work for
fields like LastUpdatedBy and OwnerName, but not for Requestors.
I still have $UsernameFormat set, by default, to “concise”, but in the
dashboard for the requestor column I get email addresses.

Do users for those requestors actually have usernames that aren’t their
email addresses? Check in the admin UI.

Thomas

RT Training Sessions (http://bestpractical.com/services/training.html)

  • Chicago, IL, USA September 26 & 27, 2011
  • San Francisco, CA, USA October 18 & 19, 2011
  • Washington DC, USA October 31 & November 1, 2011
  • Melbourne VIC, Australia November 28 & 29, 2011
  • Barcelona, Spain November 28 & 29, 2011

yes, they do. For example in the dashboard I have both the Requestor and
LastUpdatedBy fields. For the same person I get the full email in the
Requestor field and the username in the LastUpdatedBy field…

Just looked at the column map in
share/html/Elements/RT__Ticket/ColumnMap and Requestors is always a
comma separate list of email addresses in search results. You could use
the Once there callback to add your own column, RequestorNames or
RequestorFormatted (and use ShowUser).

GitHub - bestpractical/rtx-ticketlisttransactions has
examples of the two callbacks you’d want to hook.

Thomas

Thomas,

You could use the Once there callback to add your own column,
RequestorNames or RequestorFormatted (and use ShowUser).

GitHub - bestpractical/rtx-ticketlisttransactions has
examples of the two callbacks you’d want to hook.

thanks a lot. I used the callback as you suggested and it’s working
great! Thanks also for the examples, they were very helpful.

Daniel.