The data collected by the two-dimensional filter is incomplete. Only the first few consecutive data can be counted, and the subsequent data cannot be counted.
1 -1
2- 1
3- Null
4-1
The Total number should be:1+1+1=3
But it is:1+1=2
You can find that the total number counted by the above widget is 28+3+1=32. Then we open the filter of this project and find that the actual total is 100+, but the component can only count the part with consecutive numbers in front. When encountering Items marked in red are empty values and cannot be counted even if there is non-empty data on subsequent pages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian Community!
We need some more information to enable us to explain what is happening here.
What do you mean by "1 -1", "2- 1", "3-null" and "4-1"?
Where is 1+1+1=3 being shown?
Could you expand on what you mean by "Only the first few consecutive data can be counted" and what "subsequent data" is?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can't see anything wrong with the widget - it's adding up 28 + 3 + 1 + 1043 as it should do. Your second screenshot does not appear to be showing the field that you are using for the axis in the gadget either, so I'm not sure what you're trying to show us here.
Jira does not tend to display data that is empty. If there's a zero count for an option in the gadget, there's no point displaying it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I mean there should be numbers greater than 0,but it actually displays 0 in the widget .
In the filter detail list, there are more than 28+3+1 items have been filled in numbers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you show us a filter result that shows issues that have values for the fields showing as 0 in the widget?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The screenshot you've given us shows a filter returning 35 results, but three of them have values that are not 0 in them, which suggests that the gadget is working fine.
I think we need to go back to the basics and look at exactly what the underlying filters are doing.
Could you give us the text of the filter that the gadget is using?
Ideally, just the plain text, so I can copy and paste the text I can't read or write. The next steps are going to be me asking what the results of filters are, and they will be like
project = x and Panda is > 0
and
project = x and (the character at the bottom of the first column in your first screenshot is) is not empty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
project = ICS0705 AND issuetype =缺陷
---Tolal 1085
project = ICS0705 AND issuetype =缺陷 AND 重新打开次数 is EMPTY
-Total 449
project = ICS0705 AND issuetype =缺陷 AND 重新打开次数 is not EMPTY
-Total 32
1085!=449+32
If I export the 1085 items to Excel,I can get 81 items which "重新打开次数” is not empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, that suggests a broken index is a possibility.
The next thing to do is re-index the project - as a project or jira admin, go to the project settings (for ICS0705) and find the re-index option. Let that complete and then re-run the three queries.
If the numbers are now right, it was the index. If they are still 1085, 449 and 32 (or if the new numbers for 449 and 32 do not add up to the new 1085), then it is not the index directly.
The other thing I can think of that might be problems are a bit technical, and not worth exploring until we have eliminated simple indexing errors ( indexing language and database collation settings can cause odd things to happen in searches)
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.