Fixes #2405

If I am correct the length of issues is "all" the issues that were ever opened/assigned (whether they are open or closed). Shouldn't we just use assigned_open_count & opened_issue_open_count, and drop the issues length?

This feels sub-optimal, imagines you have 1000 tickets of which only 2 are open, you still need to go through these 1000 just to count 2.
Let's just ask the DB for the right info then.

@pingou i get your point. Can we just fetch the open issues at first and if the user clicks on 'closed' or 'all' then we fetch the rest?

Simpler idea: what about using JS to count the number of issues? We're already using it to figure out what to show and what not to, we could just ask it how many items of a certain class are shown and update live the count.

What do you think?

i did think of this and now i can't think of any reason why i didn't proceed that way :cry:

@vivekanand1101 still working on this one?

@vivekanand1101 still working on this one?

No, i don't think i will get time and this PR is practically useless. You should close