delta/gitlab/gitlab-ce.git/app/controllers/dashboard_controller.rb, branch github-import-docs gitlab.com: gitlab-org/gitlab-ce.git Fixed dashboard filtering tests 2018-04-03T18:19:20+00:00 Jan Provaznik jprovaznik@gitlab.com 2018-03-27T15:29:13+00:00 d10416e231a27c63c322ba7338f2ea8279436336 






Check if at least one filter is set on dashboard
2018-04-03T18:19:09+00:00

Jan Provaznik
jprovaznik@gitlab.com

2018-03-23T14:27:15+00:00

c1b71e2fa1e49da82b15ee7f12148a372face09c

When listing issues and merge requests on dasboard page,
make sure that at least one filter is enabled.

User's id is used in search autocomplete widget instead
of username, which allows presetting user in filter dropdowns.

Related to #43246





When listing issues and merge requests on dasboard page,
make sure that at least one filter is enabled.

User's id is used in search autocomplete widget instead
of username, which allows presetting user in filter dropdowns.

Related to #43246







Resolve "DashboardController#activity.json is slow due to SQL"
2017-11-06T16:52:56+00:00

Francisco Javier López
fjlopez@gitlab.com

2017-11-06T16:52:56+00:00

bf0331dc72db658b012d58e33ca47da6d8f99d46












Use a specialized class for querying events
2017-08-10T15:45:49+00:00

Yorick Peterse
yorickpeterse@gmail.com

2017-07-27T17:42:15+00:00

aac1de46c9be659b74da12f704412f38292974db

This changes various controllers to use the new EventCollection class
for retrieving events. This class uses a JOIN LATERAL query on
PostgreSQL to retrieve queries in a more efficient way, while falling
back to a simpler / less efficient query for MySQL.

The EventCollection class also includes a limit on the number of events
to display to prevent malicious users from cycling through all events,
as doing so could put a lot of pressure on the database.

JOIN LATERAL is only supported on PostgreSQL starting with version 9.3.0
and as such this optimisation is only used when using PostgreSQL 9.3 or
newer.





This changes various controllers to use the new EventCollection class
for retrieving events. This class uses a JOIN LATERAL query on
PostgreSQL to retrieve queries in a more efficient way, while falling
back to a simpler / less efficient query for MySQL.

The EventCollection class also includes a limit on the number of events
to display to prevent malicious users from cycling through all events,
as doing so could put a lot of pressure on the database.

JOIN LATERAL is only supported on PostgreSQL starting with version 9.3.0
and as such this optimisation is only used when using PostgreSQL 9.3 or
newer.







Remove some deprecated methods
2017-05-30T21:24:17+00:00

Toon Claes
toon@gitlab.com

2017-05-30T21:24:17+00:00

1e5506d01619780da68fc51ada58188a9070255b

To avoid the use of slow queries, remove some deprecated methods and encourage
the use of ProjectFinder to find projects.





To avoid the use of slow queries, remove some deprecated methods and encourage
the use of ProjectFinder to find projects.







Consistently display last push event widget
2017-05-25T20:21:30+00:00

Douwe Maan
douwe@selenight.nl

2017-05-20T19:27:35+00:00

e45e540d1d90549cc5f45521360241afce9eaf18












Present group and dashboard MR list without grouping by project
2017-01-27T22:20:18+00:00

Oswaldo Ferreira
oswaldo@gitlab.com

2017-01-10T23:52:25+00:00

aeb9db6753cfdd56f82d80c0e2c01f63d65b705d












Restrict starred projects to viewable ones
2016-05-10T17:13:52+00:00

Sean McGivern
sean@gitlab.com

2016-05-10T17:03:55+00:00

97424ea544d0954e582a356586270e983d3bbb7a

`User#starred_projects` doesn't perform any visibility checks. This has
a couple of problems:

1. It assumes a user can always view all of their starred projects in
   perpetuity (project not changed to private, access revoked, etc.).
2. It assumes that we'll only ever allow a user to star a project they
   can view. This is currently the case, but bugs happen.

Add `User#viewable_starred_projects` to filter the starred projects by
those the user either has explicit access to, or are public or
internal. Then use that in all places where we list the user's starred
projects.





`User#starred_projects` doesn't perform any visibility checks. This has
a couple of problems:

1. It assumes a user can always view all of their starred projects in
   perpetuity (project not changed to private, access revoked, etc.).
2. It assumes that we'll only ever allow a user to star a project they
   can view. This is currently the case, but bugs happen.

Add `User#viewable_starred_projects` to filter the starred projects by
those the user either has explicit access to, or are public or
internal. Then use that in all places where we list the user's starred
projects.







Fix an issue causing the Dashboard/Milestones page to be blank
2016-03-23T11:02:15+00:00

Rémy Coutable
remy@rymai.me

2016-03-22T18:19:53+00:00

7dc16346bba174d6075cf438adcd70a5596ba935












Dedupe labels in labels selector in Dashboard pages
2016-03-18T20:49:56+00:00

Rémy Coutable
remy@rymai.me

2016-03-18T20:49:56+00:00

733ae58798f6736af156e94b6906ac9c0b76fa3d

Also moved useless helper methods and directly to the
DashboardController.





Also moved useless helper methods and directly to the
DashboardController.