gitlab-org--gitlab-foss/app/views/shared/_issues.html.haml

= render 'shared/alerts/positioning_disabled'

- if @issues.to_a.any?
  %ul.content-list.issues-list.issuable-list{ class: issue_manual_ordering_class, data: { group_full_path: @group&.full_path } }
    = render partial: 'projects/issues/issue', collection: @issues
  = paginate @issues, theme: "gitlab"
- else
  - project_select_button = local_assigns.fetch(:project_select_button, false)
  = render 'shared/empty_states/issues', project_select_button: project_select_button
Add latest changes from gitlab-org/gitlab@master 2021-05-17 14:10:42 -04:00			`= render 'shared/alerts/positioning_disabled'`

Save a query on issue and MR lists `any?` on an AR relation performs a `SELECT COUNT`, which we don't need. 1. We are very likely to have issues or MRs, so the `SELECT COUNT` is often unnecessary. 2. Even where there are no items returned, the overhead of the `SELECT *` instead of `SELECT COUNT` is relatively small. Calling `to_a` on the relation lets us use `Enumerable#any?`, which will return immediately if there are objects returned. 2016-11-25 08:41:13 -05:00			`- if @issues.to_a.any?`
Add latest changes from gitlab-org/gitlab@master 2021-05-17 14:10:42 -04:00			`%ul.content-list.issues-list.issuable-list{ class: issue_manual_ordering_class, data: { group_full_path: @group&.full_path } }`
Add latest changes from gitlab-org/gitlab@master 2020-11-30 07:09:21 -05:00			`= render partial: 'projects/issues/issue', collection: @issues`
Dashboard/Group issues and mr pages refactoring 2013-08-06 14:12:01 -04:00			`= paginate @issues, theme: "gitlab"`
			`- else`
Add latest changes from gitlab-org/gitlab@master 2021-04-01 02:09:29 -04:00			`- project_select_button = local_assigns.fetch(:project_select_button, false)`
			`= render 'shared/empty_states/issues', project_select_button: project_select_button`