Fix issue overview for teams (#19652)

- Don't use hacky solution to limit to the correct RepoID's, instead use
current code to handle these limits. The existing code is more correct
than the hacky solution.
- Resolves #19636
- Add test-case

models/fixtures/issue.yml

@@ -184,3 +184,27 @@
   is_pull: false
   created_unix: 1602935696
   updated_unix: 1602935696
+
+-
+  id: 16
+  repo_id: 32
+  index: 1
+  poster_id: 2
+  name: just a normal issue
+  content: content
+  is_closed: false
+  is_pull: false
+  created_unix: 1602935696
+  updated_unix: 1602935696
+
+-
+  id: 17
+  repo_id: 32
+  index: 2
+  poster_id: 15
+  name: a issue with a assignment
+  content: content
+  is_closed: false
+  is_pull: false
+  created_unix: 1602935696
+  updated_unix: 1602935696

models/fixtures/issue_assignees.yml

@@ -10,3 +10,7 @@
   id: 3
   assignee_id: 2
   issue_id: 6
+-
+  id: 4
+  assignee_id: 2
+  issue_id: 17

models/fixtures/issue_index.yml

@@ -10,6 +10,9 @@
 -
   group_id: 10
   max_index: 1
+-
+  group_id: 32
+  max_index: 2
 -
   group_id: 48
   max_index: 1
@@ -21,4 +24,4 @@
   max_index: 1
 -
   group_id: 51
-  max_index: 1
+  max_index: 1

models/fixtures/repository.yml

@@ -483,7 +483,7 @@
   is_private: false
   num_stars: 0
   num_forks: 0
-  num_issues: 0
+  num_issues: 2
   is_mirror: false
   status: 0
 

models/fixtures/team_unit.yml

@@ -252,6 +252,7 @@
 
 -
   id: 43
+  org_id: 3
   team_id: 7
   type: 2 # issues
   access_mode: 2