Page tree
Skip to end of metadata
Go to start of metadata

Problem

  • Time to SLA field could not be used while searching issues.
  • Issues could not be ordered with their Time to SLA values in issue navigator.
  • Getting following error while upgrading TTS v7.

    Field 'Time to SLA' does not exist or you do not have permission to view it.

Causes

Time to SLA displays the remaining time of SLAs and naturally its value constantly changes. Since JIRA requests updated values from TTS plugin each time Time to SLA field is displayed we can show you correct values with custom field view. However when you search with Time to SLA field JIRA obtains these values from underlying indexing mechanism which might holding out-dated value for a Time to SLA field thus generating wrong results.

In order to prevent possibly incorrect results caused by these shortcomings, searching and ordering is not possible with Time to SLA field.

Possible Workarounds

Searching: You can use TTS JQL functions in order to make searches with remaining time or overdue of SLAs as in the examples:

issue in tts.issuesRemainingSlaGreaterThan('2d')
issue in tts.issuesWithBreachLongerThan('5d', 'First Response SLA')

You can find details about JQL functions here.

Note: Prior to v7, Time to SLA field was searchable but this feature was based on the target dates of SLA not the remaining times. You can still obtain this behaviour by using SLA Dates field with setting it to first SLA target date


Ordering: Currently there is no possible way to order issues by their remaining working times. However you can use SLA Dates custom field to order issues by their first SLA target date.

Note: Prior to v7, Time to SLA field was orderable but this feature was working as same as the SLA Dates alternative mentioned above.

Our Plans

We are working on alternatives to provide you a better and consistent way to sort and order your SLAs with Time to SLA field. Biggest drawback here is the nature of SLAs since their remaining time constantly changes and we would like to provide a solution capable of handling this behaviour while being lightweight enough to not disrupt your JIRA operations.

  • No labels