| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
RelativePositioning module was heavily dependent on the Issue model.
This changes makes it easier to reuse the functionality provided by
RelativePositioning in other models.
Needed by: https://gitlab.com/gitlab-org/gitlab-ee/issues/12196
|
| |
|
|
| |
and state
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Next models are affected:
* Project
* Namespace
* Issue
* Merge request
* CI Trigger
* CI Pipeline schedule
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |\
| |
| |
| |
| | |
Expose merge requests count based on user access
See merge request gitlab/gitlabhq!3157
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Count issues related merge requests based on user access level. And
issue can have related MRs from projects where user does not have
access so the number of related merge requests should be adjusted
based on user's ability to access the related MRs.
https://gitlab.com/gitlab-org/gitlab-ce/issues/59581
|
| |/
|
|
|
| |
Based on review comment fetching labels hook_attrs is now
wrapped in an issue's model method.
|
| |
|
|
|
| |
- adding a "Manual" option to the dropdown
- show 100 issues list when manually sorting
|
| |
|
|
| |
spec/features/groups/group_page_with_external_authorization_service_spec to EE
|
| |
|
|
|
| |
Backports https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10161
(code out of ee/ folder).
|
| | |
|
| |
|
| |
This reverts merge request !26823
|
| |
|
|
| |
spec/features/groups/group_page_with_external_authorization_service_spec to EE
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
By preloading associations and batching issuable metadata lookups,
we can significantly cut the number of SQL queries needed to load
the Todos API endpoint.
On GitLab.com, my own tests showed my user's SQL queries went
from 365 to under 60 SQL queries.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40378
|
| |
|
|
| |
Move logic of obtaining Issuable data to separate method
|
| |
|
|
|
| |
'master'"
This reverts merge request !25042
|
| |
|
|
| |
Move logic of obtaining Issuable data to separate method
|
| |
|
|
|
|
|
| |
Ability to filter confidential issues
Closes #50747
See merge request gitlab-org/gitlab-ce!24960
|
| |
|
|
|
| |
This reverts commit d133bf84c668df3dfc9938bb04150754cb873c8b, reversing
changes made to 7981c0292b07a0138b096fa082341fcb13e9ce2b.
|
| | |
|
| |
|
|
|
|
| |
In order to let users' sorting preferences transfer between devices, we
save the preference for issues and MRs (one preference for issues, one
for MRs) in the backend inside the UserPreference object
|
| |
|
|
|
|
|
|
|
| |
Spam checks are meant for content that could be indexed by search
engines. Confidential issues aren't indexed by search engines, so we
don't need to do spam checks for them.
We do need to check for spam when an issue changes from confidential to
public, even if nothing else changed.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
1. When every issue has a relative position set, we don't need to
perform any updates, or calculate the maximum position in the parent.
2. If we do need to calculate the maximum position in the parent, many
parents (specifically, groups with lots of projects) leads to a slow
query where only the index on issues.relative_position is used, not
the index on issues.project_id. Adding the GROUP BY forces Postgres
to use both indices.
|
| |
|
|
| |
This reverts commit 8c126525faba40032244328187ba73a53b6eaf4c.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
In order to ensure we have the right endpoint to query for an
issue's possible valid labels, we store that url in the issue
object that gets passed to the frontend.
|
| |
|
|
|
| |
Moves the related_branches method from Issue model
to RelatedBranchesService
|
| |
|
|
|
| |
This whitelists all existing offenses for the various CodeReuse cops, of
which most are triggered by the CodeReuse/ActiveRecord cop.
|
| |
|
|
|
|
|
|
| |
These methods don't really need to be on the Issue model. Issue#related_branches
can also be moved to a service, but we can do that in a separate commit.
This commit does not change any behaviour; it just moves code around, renames
the service, and refactors the specs.
|
| |\
| |
| |
| |
| | |
Group todos
See merge request gitlab-org/gitlab-ce!20675
|
| | |
| |
| |
| | |
This reverts commit 8717c7dad9b5a8fa21ec9a652c54718a6b4c2175.
|
| |\ \
| |/
|/|
| |
| | |
Enable frozen string in app/models/*.rb
See merge request gitlab-org/gitlab-ce!20851
|
| | |
| |
| |
| | |
Partially addresses #47424.
|
| |/ |
|
| |
|
|
|
| |
This reverts commit 4d9a3f42f1fd3be21555e19872b7121cca65015e, reversing
changes made to ecf9c145f6e4d170cd059df88743393d9e63c489.
|
| |
|
|
|
|
|
| |
* Group filtering now includes also issues/MRs from
subgroups/subprojects
* fixed due_date
* Also DRYed todo controller specs
|
| | |
|
| | |
|
| |\ |
|
| | |\
| | |
| | |
| | |
| | | |
Take two for MR metrics population background migration
See merge request gitlab-org/gitlab-ce!19097
|
| | | | |
|
| | |/ |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This reverts the addition of the "goldiloader" Gem and all use of it.
While this Gem is very promising it's causing a variety of problems on
GitLab.com due to it eager-loading too much data in places where we
don't expect/can handle this. At least for the time being this means we
have to go back to manually fixing N+1 query problems, but at least
those should not cause a negative impact on availability.
|
