Difference between revisions of "ManualTicketDates"

From Request Tracker Wiki
Jump to navigation Jump to search
Line 10: Line 10:
* Starts
* Starts
* Started
* Started
* Resolved
* Last Contact
* Due
* Due
* Told
* Closed
* LastUpdated
* Updated


Starts and Due dates work like expected (planned) time boundaries, while Started and Resolved are set after things happen. How this works is described below.
Starts and Due dates work like expected (planned) time boundaries, while Started, Last Contact, Closed, and Updated are set after things happen. How this works is described below.


= Description =
= Description =
Line 40: Line 40:
There are no restrictions on these dates, so work on ticket could begin (started) earlier than it was expected (starts) or vice versa.
There are no restrictions on these dates, so work on ticket could begin (started) earlier than it was expected (starts) or vice versa.


== Resolved ==
== Last Contact ==


Resolved date indicates time when the ticket has been closed and RT set it automatically when user or [[Scrip]] changes status of the ticket to inactive value (see also [[InactiveStatus]]).
Is set when inbound user replies to a ticket or can be set manually. Last time that requestors were notified by someone.


== Due ==
== Due ==
Line 48: Line 48:
Due date defines a deadline for the ticket. You can implement SLA or projects' deadlines using this field. Editable and optional.
Due date defines a deadline for the ticket. You can implement SLA or projects' deadlines using this field. Editable and optional.


== Told (Last Contact) ==
== Updated ==
 
Is set when inbound user replies to a ticket or can be set manually. Last time that requestors were notified by someone.
 
== LastUpdated ==


This date is set automatically to now when ticket is changed in any way.
This date is set automatically to now when ticket is changed in any way.
Line 58: Line 54:
= Changing dates =
= Changing dates =


Users who have the correct rights can set Starts, Started, Told and Due dates. These dates and others can be set automatically as described above.
Users who have the correct rights can set Starts, Started, Last Contact, and Due dates. These dates and others can be set automatically as described above.


To change a date, open a ticket and click on title of the 'Dates' box or 'Dates' subtab in the menu. From this page, you can adjust dates of the ticket.
To change a date, open a ticket and click on title of the 'Dates' box or 'Dates' subtab in the menu. From this page, you can adjust dates of the ticket.


To change any of these dates, type the new date in the text box and click the Submit button. In recent versions you can use calendar popup to pick a date.
To change any of these dates, type the new date in the text box or use the calendar popup to pick a date, then click the Submit button.


'''NOTE:''' Acceptable date formats such as mm/dd/yy or dd/mm/yyyy vary by organization and country. If you're not sure, ask an administrator how to enter dates. Administrators can consult with [http://search.cpan.org/author/MUIR/Time-modules-2003.0211/lib/Time/ParseDate.pm manual] for a date parsing perl module.
'''NOTE:''' Acceptable date formats such as mm/dd/yy or dd/mm/yyyy vary by organization and country. If you're not sure, ask an administrator how to enter dates. Administrators can consult with [https://metacpan.org/pod/Time::ParseDate manual] for a date parsing perl module.


Dates can also be changed from the bulk update option. See [[ManualTicketsBulkUpdate]].
Dates can also be changed from the bulk update option. See [[ManualTicketsBulkUpdate]].
Line 70: Line 66:
== Unset (delete) Date ==
== Unset (delete) Date ==


To delete date or clear date, simply enter the number 0 in the date field and save. This will change the date field to "not set". '''This totally sounds like a bug and should be fixed'''.
To delete date or clear date, simply remove the date from the text box and save. This will change the date field to "not set".


= Searching by dates =
= Searching by dates =
Line 77: Line 73:


= Working with date in scripts =
= Working with date in scripts =
If you need to search for the dates in script, consult [https://docs.bestpractical.com/rt/4.2.15/RT/Date.html official docs]. To display the correct local time shift use <tt>Timezone => ‘user’</tt> in your functions. Example:
If you need to search for the dates in script, consult [https://docs.bestpractical.com/rt/4.4.4/RT/Date.html official docs]. To display the correct local time shift use <tt>Timezone => ‘user’</tt> in your functions. Example:
   $date->Set(Format => ‘ISO’,Value => $ticket->Created);
   $date->Set(Format => ‘ISO’,Value => $ticket->Created);
   say $date->LocalizedDateTime(Timezone => ‘user’);
   say $date->LocalizedDateTime(Timezone => ‘user’);

Revision as of 10:12, 20 March 2019

Up: ManualUsingWebInterface


Introduction

Tickets in RT have several date fields:

  • Created
  • Starts
  • Started
  • Last Contact
  • Due
  • Closed
  • Updated

Starts and Due dates work like expected (planned) time boundaries, while Started, Last Contact, Closed, and Updated are set after things happen. How this works is described below.

Description

Created

This is the first date that is set during creation of a ticket and cannot be changed using the UI.

Starts

Starts date is used to indicate the time when staff expects to begin to work on the current ticket. Editable and optional.

Started

RT uses Started date to indicate the time when a user actually begins work on the ticket. This date is set to "now" automatically when status of the ticket is changed from 'new' to any other value. So if the server is configured to 'auto open' tickets on correspond, then it's set on correspond. However, if somebody opens it before any correspondence then it's also set.

Try next tests:

  • create a ticket, click the open action and look on the dates box
  • create a ticket, click the resolve action and look on the dates box

Starts vs. Started

There are no restrictions on these dates, so work on ticket could begin (started) earlier than it was expected (starts) or vice versa.

Last Contact

Is set when inbound user replies to a ticket or can be set manually. Last time that requestors were notified by someone.

Due

Due date defines a deadline for the ticket. You can implement SLA or projects' deadlines using this field. Editable and optional.

Updated

This date is set automatically to now when ticket is changed in any way.

Changing dates

Users who have the correct rights can set Starts, Started, Last Contact, and Due dates. These dates and others can be set automatically as described above.

To change a date, open a ticket and click on title of the 'Dates' box or 'Dates' subtab in the menu. From this page, you can adjust dates of the ticket.

To change any of these dates, type the new date in the text box or use the calendar popup to pick a date, then click the Submit button.

NOTE: Acceptable date formats such as mm/dd/yy or dd/mm/yyyy vary by organization and country. If you're not sure, ask an administrator how to enter dates. Administrators can consult with manual for a date parsing perl module.

Dates can also be changed from the bulk update option. See ManualTicketsBulkUpdate.

Unset (delete) Date

To delete date or clear date, simply remove the date from the text box and save. This will change the date field to "not set".

Searching by dates

It's possible to search using not only absolute dates like '2009-11-30', but also relative dates like '7 days ago'. This is described more in details at Ticket SQL.

Working with date in scripts

If you need to search for the dates in script, consult official docs. To display the correct local time shift use Timezone => ‘user’ in your functions. Example:

 $date->Set(Format => ‘ISO’,Value => $ticket->Created);
 say $date->LocalizedDateTime(Timezone => ‘user’);
 say $date->ISO(Timezone => ‘user’);

Up: ManualUsingWebInterface