2

1

I'm trying to add a custom search to a filter that will only show cases that have any amount of time logged against them in order to get a list of cases that are "in progress". It seems reasonable to me that the smallest unit of time that would be considered for this should be 1 minute, so I've tried using the search elapsedtime:"1m.."

This doesn't seem to do anything. However, changing it to elapsedtime:"1h.." does indeed filter out any cases with less than an hour of work on them.

So, I tried:

  • elapsedtime:"1m.." - all cases still visible
  • elapsedtime:"1h.." - works!
  • elapsedtime:"30m.." - all cases still visible
  • elapsedtime:"59m.." - works!
  • elapsedtime:"31m.." - works!
  • elapsedtime:"29m.." - all cases still visible
  • elapsedtime:"21m.." - all cases still visible

This doesn't make sense to me - can anyone tell me what's going on here, and if/how it's possible to correctly construct the filter I'm looking for?

flag

2 Answers

2

That does sound like a bug.

Consider using

-elapsedtime:"0m"

(i.e. "Elapsed time is not 0m").

link|flag
Perfect! While it looks like I indeed might've found a bug, this is actually a better solution for what I'm trying to do. Thanks! – Daniel Schaffer Jun 16 2010 at 17:12
0

Apparently, all values below 0.505h (or 30.3m) are truncated to 0. It sounds like a bug to me.
Decimals are allowed, so as soon as this is fixed you can use elapsedtime:0.001m...

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.