tts.issuesWithRemainingTimeLessThan shows wrong results

Issue #432 resolved
Simon Bauer created an issue

Hey everyone,

just a quick question: I've set up a filter containing the term issue in tts.issuesWithRemainingTimeLessThan(10d) Why do I get results where the SLA times are substantially longer than 10 days? I guess I'm doing something wrong here.

You can see the full JQL query as well as filter results in the following screenshot:


Thanks in advance and cheers, Simon.

Comments (12)

  1. Tuncay Senturk repo owner

    Hi Simon,

    It seems that you did nothing wrong. We need to investigate this.
    Thanks for your patience.


  2. Simon Bauer reporter

    Hey Tuncay,

    any update on this? We want to use this JQL query on a wallboard, but delivering the wrong results, it's pretty much useless right now.

    Cheers, Simon.

  3. Kubilay Karpat

    Hi Simon

    Could you please share screenshots of

    • the definition of Standard Fixed/Workaround and Standart Resolution SLAs
    • and the history tab of one of the issues with this problem.

    Best, Kubilay

  4. Simon Bauer reporter

    Hi Kubilay, here are the requested screenshots:

    Standard SLA configuration: standard.PNG

    Standard pause conditions: standard_pause.PNG.png

    Issue history: history.png

    Cheers, Simon.

  5. Kubilay Karpat

    Hi Simon,

    Sorry for late response we had a long national holiday here. We are analyzing your problem will update you as soon as possible.

    Best, Kubilay

  6. Kubilay Karpat

    Hi Simon,

    We have been located the problem and fix will be ready soon.

    Days in Time to SLA field are working days and as you know those 'working days' are shorter than 24h if you define a custom calendar. Problem here that Time to SLA fields calculations based on 1d = 1 working day and remaining time JQLs calculations based on 1d = 24. We will correct those 2 affected JQls (issuesWithRemainingTimeMoreThan and issuesWithRemainingTimeLessThan) behavior to work concurrently with Time to SLA fields.

    Best, Kubilay

  7. Kubilay Karpat

    Hi again,

    We released 6.28.0 and it contains a fix for this problem. If you have any further problems please raise a ticket from TTS Service Desk. Thanks for your feedback...

    Best, Kubilay

  8. Simon Bauer reporter

    Hi Kubilay,

    that's good to hear! We currently have 5.30.1 installed and I don't see any update options. Do I have to do this manually?

    Cheers, Simon.

  9. Kubilay Karpat

    Hi Simon,

    As you might know Atlassian ended support for JIRA 6 a while ago and we also ended our support to JIRA 6 recently in order to deliver better and frequent updates. Do you have a plan for moving to JIRA 7?

    Best, Kubilay

  10. Simon Bauer reporter

    Thanks, that is what I suspected.

    We're planning to move within the next few weeks. Problem is that we run a self-created webinterface for Jira which has to be adjusted first.

    Cheers, Simon.

  11. Kubilay Karpat

    Nice to hear that you are moving soon. We made quite nice improvements since 5.30.1 including some significant performance updates for JQLs and SLA calculations. I hope that you will have a better experience.

    Always feel free to raise a ticket and ask a question. We glad to hear from you. Have a nice day...

    Best, Kubilay

  12. Log in to comment