Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning
titleImportant Notes and Disclaimer
  • Information stored in database by Time to SLA plugin is never meant to be used externally. We do not guarantee the integrity of the information you have collected by those instructions here. Use them by at your own risk.
  • Database tables stores vital information for Jira, Time to SLA and many other plugins. Manually working on it might cause irreversible damage or bad application performance due to corrupted table statistics etc.
  • When possible use REST services instead. If something missing from REST services please raise a ticket and we will do our best to provide related services.

...

  • Data on this table only updated during issue transitions. 
    • This is why you might observe inconsistencies between SLA information on issue view. Because SLA is a an active metric for example remaining duration for an active SLA changes with each second.
    • SLAs are considered as breached once their deadline has been passed yet this is not persisted on database until they go through an issue transition after breaching their deadline.
    • One exception for that is paused SLAs. Target dates of paused SLAs will be always kept updated. (This is done by a scheduled task so that it is normal to observe 2-3 minutes inaccuracies.)
  • Completed SLAs (SLAs that reached their target status) always shows updated information since there is no actively running clock on them.
    • So if you see FINISHED column true you can be sure that all values in other columns are will be consistent with actual SLA state.
  • EXPECTED_TARGET_DATE is a good reference to check whether or not an SLA is breached. It does not change by time (except when an SLA is paused in that case target date shifts further in time and this is properly reflected on database entries with help of a scheduled task.)


Here is are some queries to differentiate different SLA states:

...