Sometimes the issue and MR list are empty

https://gitlab.com/gitlab-org/gitlab-development-kit/issues

@yorickpeterse Cache issue?

/cc @jschatz1

@vsizov Assuming this is a frontend issue. Can you explain any other details about how to reproduce other than visiting the page?

Wow the problem is more global, I don't see any issues or MR's at that page. When I go to that page with another browser I see all issues and MRs. It looks like AJAX request has been cached.

@jschatz1 I didn't do any special things to see this bug. I just went to that project/page.

cc @iamphill can you check this out since you did the issue page ajax stuff?

@sytses Reported yesterday in the operations chat that he didn't find some issue in the list as well. I didn't see that issue either by the way. It could be related.

@vsizov I'll check this out right now.

sytse [9:54 PM] https://gitlab.com/gitlab-com/operations/issues?>scope=all&sort=milestone_due_desc&state=opened&utf8=%E2%9C%93&author_id=1 doesn't contain >https://gitlab.com/gitlab-com/operations/issues/182 Is this due to Elasticsearch being behind?

@vsizov I don't think this is a frontend issue. I don't think it's being cached from our end.

@vsizov As far as I'm aware we don't cache issue counts.

Title changed from Wrong counter value to Sometimes the issue and MR list are empty

I know what the problem is. It drove me crazy :) because it seemed like related to my browser only. I removed the issuable_sort cookie and everything has been shown.

Steps to reproduce: Go to the project where there is no any milestone and choose issues sorting by "Milestone due soon" and all issues and MRs will be hidden. This is a bug itself, but the worse thing is that this option will be applied to any project I go since the state is stored in a cookie.

@jschatz1 I'll add frontend label

Added frontend ~12980 labels

Reassigned to @felipe_artur

I think we should keep that behavior of saving filter state.
My suggestion is to show issues without milestones at the end when this option is selected.

What do you think?

There is another problem with this filter:

When i am filtering by milestone/author/assignee/label/weight and select any filter in the right dropdown,
the state is lost so i have to select all the options again. We should keep the state of all dropdowns.

I fixed the issue with filtering not persisting in the sort dropdown in !3699 (merged)

@vsizov Thanks for figuring this out. @felipe_artur I think your second issue is fixed thanks to @iamphill. The first issue: If the cookie is saved on a per project basis does that solve everything?

@iamphill Thanks =)

Another suggestion is to display a better message when search returns empty. instead of

No issues to show

We should go with:

No issues found matching this filter.

@jschatz1 I made a small commit about saving cookie per project/group https://gitlab.com/gitlab-org/gitlab-ce/commit/e7c268a26ea2a1da4a52c49bf43f33bdf6acaeda.
It can be a good feature, however i don't think it will solve the problem.
I think the right dropdown in the filter is about ordering and not filtering elements, this can be confusing to the user since the left dropdowns are supposed to do the filtering.

In my opinion the best solution in the case should be showing Merge requets/Issues without a milestone at the beginning or at the end of the results list.

@felipe_artur MR?

mentioned in merge request !3950 (merged)

@jschatz1 !3950 (merged)

Another suggestion: When i am ordering by column i d like to see the context value on the list.
For example, when i select to order by "most popular" i d like to see the number of votes in each Issue/MR on the results list. The same should happen to all other columns.

Makes sense?

@felipe_artur can you make separate issues for these other items?

mentioned in issue #17006 (closed)

Milestone changed to 8.8

Status changed to closed by merge request !3950 (merged)

Hi all.

I see the same bug in GitLab Enterprise Edition 8.9.6-ee a530eae on gitlab.com. Screenshot attached.

Best

Alex

@ak_nuuk It looks like you look at "Closed" issues but you have 3 open :) Maybe I'm wrong, it would be great if you make full screenshot with no overlapping, so we will be sure ;)

I just checked, the fix is actually pushed to v8.9.x (https://gitlab.com/gitlab-org/gitlab-ee/commit/996240a4895abddf069eb6fc195bacee5e344e16)

Hi @vsizov

Attached 2 screenshots. I can not see what I'm doing wrong. I also checked the filter... :-(

Best

Alex

@ak_nuuk Ah sorry, our new UI has a global sidebar which is not related to any particular project, so your "Issues" on sidebar are not related to this particular project, it's your global issues. So it looks like you have no issues in the project.

@vsizov There are open issues in this project. The issues are not assigned to me but they are open. I can see them all in the activity screen and show the detail view for each issue - but I dont see the issues (that are not assigned to me) in the issue overview for the project. It looks like a bug for me. Right now I only see one issue (assigned to me) in the issue overview. Attached the activity screen:

@ak_nuuk Your last screenshot shows that you have one issue in the project, I see it in top menu but look at your previous screenshots. They are empty. Why?

@vsizov "Right now I only see one issue (assigned to me) in the issue overview"

@ak_nuuk OK. Those issues are not confidential right? Could you also try to clear the cookies? maybe it's related somehow to previous bug.

@iamphill It looks weird really.

@vsizov They are confidential - sorry that I didn't mentioned that. But I'm Owner of the Group. The confidential settings dialog for each issue says "This issue is confidential and should only be visible to team members with at least Reporter access." - thought that I can see them as a Group owner.