Close ticket timestamp on Customer Portal

[assassIn]

Hey Guys,

I am bit lost after OTRS 5 to Znuny 7.1 migration. While there was no documentation or any change log i try to setup Znuny manualy step by step to meet mirror settings with "old" OTRS.

For now i try to put a close ticket timestamp for customer to see but can't figure it out. I would like to also enable customer to search/print and have that close ticket timestamp visible.
Are there some known steps to proccess that?

I count on Your experience.

Piotr

[lis9]

I hope the screenshot will help you find the settings you need.

Zrzut ekranu 2024-12-3 o 18.22.47.png

Zrzut ekranu 2024-12-3 o 18.41.43.png

Daniel

[assassIn]

Hey,

Thanks for reply. I've been in that section looking for a solution. For now i have:

attributes_view.png

search_data.png

And still all customer gets is:

customer_print_preview.png

[lis9]

Hi

Zrzut ekranu 2024-12-6 o 23.26.14.png

this setting produces close time in CSV file.

Daniel Lisiecki

[assassIn]

Thanks for a tip lis9.

I figured it out in case of searchcsv but still looking for a "Closed" field per ticket in let say TicketZoom section. I wonder if its even possible.

According to viewtopic.php?t=19274 close ticket timestamp is a part of ticket_history table "th.history_type_id = 27".

I also try to find a hint on how to create custom field so i could make ticket close timestamp from scratch. Maybe you can push me in the right direction?

[skullz]

The deafult api did not return close time..
the closest is last changed time.

1. of course, updating closed ticket will update the changed time.

Znuny_HomeCustom/Kernel/Output/HTML/Templates/Standard/CustomerTicketZoom.tt

Code: Select all

      <li>
           <span class="Key">[% Translate("Changed") | html %]:</span>
           <span class="Value" title="[% Translate(Data.Changed) | html %]">[% Translate(Data.Changed) | html %]</span>
      </li>

2. The long way, is create event module.

Example: https://github.com/znuny/Znuny/blob/dev ... nt/Test.pm

Custom module should
a) check the event (TicketStateUpdate)
b) check the current ticket state value (closed**).
b) generate current timestamp.
b) update ticket dynamic field with the timestamp.

p/s: the custom event need to be register via xml.

good luck