So I have a couple of questions.
Q1>I notice when your trying to get results if they are over 9999+ it just doesn't provide a true number is there a fix for that, or that is how it is intended?
Q2> Dashboard Question;
Code: statusCategoryChangedDate >= -8w AND status in (Closed, Done, Resolved) AND assignee in (userid)
*This should grab the last 8 weeks of data; and I have it set to show in a bar graph; I wanted to be certain; as I am not seeing the active day show up? Do I have to wait 24 hours to show the new numbers?
Q3: Current Logic;
statusCategoryChangedDate >= -1d AND status in (Closed, Done, Resolved) AND assignee in (userid)
Is there a way to show the previous day; not 1d(24hrs)? meaning I want to see yesterday's data 1201-2399; looking to identify alternate logic.
Q1.
I think it is correct, because you should limit it ti save Jira's performance.
I know how to do it on Server:
- How to increase the JIRA search results limit on the issue navigator
- Limiting the number of issues returned from a search view such as an RSS feed
Try to contact Atlassian support in Cloud case.
But my recommendation to use external BI apps to large analytical reports, for example -
eazyBI Reports and Charts for Jira Cloud
It will be more comfortable to you to work with data.
Hi, @Dan (Daniel) Newman !
Welcome to the Community!
Q3.
Yes, it is possible, for example with 2 ways:
statusCategoryChangedDate >= startOfDay(-1) and statusCategoryChangedDate <= startOfDay() AND status in (Closed, Done, Resolved) AND assignee in (userid)
or
statusCategoryChangedDate >= startOfDay(-1) and statusCategoryChangedDate <= endOfDay(-1) AND status in (Closed, Done, Resolved) AND assignee in (userid)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Q2.
If I correctly understand - you don't want to see issues that status category were changed "today".
In that case:
statusCategoryChangedDate <= startOfDay(-8w) AND status in (Closed, Done, Resolved) AND assignee in (userid)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So I wanted to see everything they have closed, done, resolved. For some reason looks like the code I am using is not displaying the current day or something is written incorrectly.
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.
@Dan (Daniel) Newman , try this query please:
statusCategory in (Done) and status changed TO (Done, Closed, Resolved) DURING (-8w, now()) AND assignee in (userid)
Also like you can see I changed construction.
In you construction it will be:
statusCategoryChangedDate >= startOfDay(-8w) and statusCategoryChangedDate <= now() AND status in (Closed, Done, Resolved) AND assignee in (userid)
Compare results and find the best one for you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Dan (Daniel) Newman
Welcome to the community.
Q1: When you say "get results" are you talking about for an issue filter? Are you talking about in the UI or using the API?
Q2: When you say you are not seeing the "active day", what exactly do you mean? Do you mean you have issues that changed Status Category (not to be confused with changing Status) on the current date and they don't show up in your results?
Q3: I'll have to think more on that one...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Q1> Dashboard Filter assignee=x status in (Closed, Done, Resolved) alltime.
Q2> Active day meaning: I am seeing a person close over 100 tickets, and the current script should see anything closed, but for w/e reason, the 100 tickets are not showing in the graph; so for some reason not sure if it needs a day to appear correctly? At least how my code is written?
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.