Hello,
i habe a simple filter in jira to list all Issues where Duedate <= Now()
if i have issues where the Duedate is between now and 31.12.2042 then the Issue is not in the result set.
if i change the date to 1.1.2043 and above then the issue is in the result set.
It seems that JIRA Time Filter dont work for timestamps which are "too much" in the feature, maybe now+20 Years ?
Anybody knwo this problem and how to solve it?
hi @Fabio Racobaldo _Catworkx_
i think a picture will help to understand the problem:
with duedate <= now() jira find also issues which are in the future and i think this is a bug.
it seems that jira is working fine with timestamps in the near future (between now and < "now+20 years") but not with timestamps which are far away in the future, like > "now+20Years") ...
I think this isn't a solution for the Problem.
because i dont waht to have all the issues in my resultset which duedate is <= startOfYear(42)
i want all issues with duedate <= now()
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
why schould i try this, your JQL is showing completly other results that i want.
i want the Issues where DueDate is reached. but it shows me issues from the future, i do not thing this is a Bug in JIRA, it simply IS a BUG in JIRA...
see the following screenshot, maybe it helps to understand the problem:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.