Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/spec/services/issues
AgeCommit message (Collapse)Author
2017-05-26Fix counters cache invalidation for Issues and Merge RequestsValery Sizov
2017-05-15[Spec optimization] Joining one-line 'it' blocksValery Sizov
2017-05-12Move update_assignee_cache_counts to the serviceValery Sizov
2017-05-10Enable the Style/TrailingCommaInArguments copRémy Coutable
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-05-06Merge branch 'blackst0ne/gitlab-ce-add_system_note_for_editing_issuable'Sean McGivern
2017-05-05Multiple issue assignee: fix for CE restrictionsValery Sizov
2017-05-05Updated specsblackst0ne
2017-05-04Backport of multiple_assignees_feature [ci skip]Valery Sizov
2017-04-26Enable RSpec/FilePath copSean McGivern
- Ignore JS fixtures - Ignore qa directory - Rewrite concern specs to put concern name first
2017-04-05Fix specsDouwe Maan
2017-04-05Add specsDouwe Maan
2017-04-05Add option to start a new discussion on an MRDouwe Maan
2017-03-29Create todos only for new mentionsJarka Kadlecova
2017-03-28Use `:empty_project` where possible in service specsRobert Speicher
2017-03-13Rename variableBob Van Landuyt
merge_request_for_resolving_discussions -> merge_request_to_resolve_discussions_of
2017-03-13Make sure the for a merge request only gets executed once.Bob Van Landuyt
2017-03-13Correctly indent quotes in new issue descriptionBob Van Landuyt
By using `>`-quote style instead of `>>>`. Also: Update documentation images.
2017-03-13Move functionality for resolving discussions into a concernBob Van Landuyt
2017-03-13Always require MR-iid for resolving discussionsBob Van Landuyt
And deduplicate the finding of MR's & discussions. Now the searching is done in the service, istead of the controller & the API.
2017-03-13Delegate a single discussion to a new issueBob Van Landuyt
Delegate a discussion in a merge request into a new issue. The discussion wil be marked as resolved and a system note will be added linking to the newly created issue.
2017-03-07Address review commentsValery Sizov
2017-03-02Satisfy rubocopValery Sizov
2017-02-28[Issue board sorting] SpecsValery Sizov
2017-02-21Spam check and reCAPTCHA improvementsOswaldo Ferreira
2017-02-12fix issue creation from milestone doesn't assign the milestonewendy0402
2017-02-07Use reCaptcha when an issue identified as spamJarka Kadlecova
2016-12-28Check if user can read issue before being assignedFelipe Artur
2016-12-16Ensure issuable state changes only fire webhooks onceMark Fletcher
* Webhooks for close and reopen events now fired in respective services only * Prevents generic 'update' webhooks firing too
2016-12-06Merge branch '23589-open-issue-for-mr' into 'master' Sean McGivern
Create an issue for all unresolved discussions in an MR See merge request !7180
2016-12-05Feature: delegate all open discussions to IssueBob Van Landuyt
When a merge request can only be merged when all discussions are resolved. This feature allows to easily delegate those discussions to a new issue, while marking them as resolved in the merge request. The user is presented with a new issue, prepared with mentions of all unresolved discussions, including the first unresolved note of the discussion, time and link to the note. When the issue is created, the discussions in the merge request will get a system note directing the user to the newly created issue.
2016-12-03Add shorthand support to gitlab markdown referencesOswaldo Ferreira
2016-12-01Only include EmailHelpers in mailer specs and specs using themRobert Speicher
2016-11-24Rephrase some system notes to be compatible with new system note styleDouwe Maan
2016-11-17Remove default value for `project` argument on subscribable concernDouglas Barbosa Alexandre
2016-11-07Process commits in a separate workerYorick Peterse
This moves the code used for processing commits from GitPushService to its own Sidekiq worker: ProcessCommitWorker. Using a Sidekiq worker allows us to process multiple commits in parallel. This in turn will lead to issues being closed faster and cross references being created faster. Furthermore by isolating this code into a separate class it's easier to test and maintain the code. The new worker also ensures it can efficiently check which issues can be closed, without having to run numerous SQL queries for every issue.
2016-10-25Merge branch '23662-issue-move-user-reference-exception' into 'master' Douwe Maan
Fix `User#to_reference` ## What does this MR do? Fix the method signature of `User#to_reference` so that moving an issue with a user reference does not throw a "invalid number of arguments" exception. ## Why was this MR needed? 1. Changes in 8.13 require `Referable`s that don't have a project reference to accept two arguments - `from_project` and `target_project`. 2. `User#to_reference` was not changed to accept the `target_project` (even though it is not used). Moving an issue containing a user reference would throw a "invalid number of arguments" exception. 3. The regression was introduced in [c8b2b3f7](https://gitlab.com/gitlab-org/gitlab-ce/commit/c8b2b3f7c32db873f1bebce3e3b1847ea24d235f#91fabb7ad88bd2fde6fef1c100a719c00e503047_75_79), which expects all `Referable`s that don't respond to `:project` to have a `to_reference` method that takes two arguments. ## Does this MR meet the acceptance criteria? - Tests - [x] Added for this feature/bug - [ ] All builds are passing - [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if it does - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? - Closes #23662 See merge request !7088
2016-10-25Fix Rubocop offenses in issue move specsGrzegorz Bizon
2016-10-25Add spec in Issues::MoveService to fix label assignment regressionStan Hu
2016-10-25Fix `User#to_reference`Timothy Andrew
1. Changes in 8.13 require `Referable`s that don't have a project reference to accept two arguments - `from_project` and `target_project`. 2. `User#to_reference` was not changed to accept the `target_project` (even though it is not used). Moving an issue containing a user reference would throw a "invalid number of arguments" exception. Fixes #23662
2016-10-19Allow users to apply group labels on Issues/MRsDouglas Barbosa Alexandre
2016-09-28Fix permission for setting an issue's due dateRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2016-09-08Add bulk update support for merge requests listDmitriy Zaporozhets
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2016-09-01Scope hooks thal will run for confidential issuesDouglas Barbosa Alexandre
2016-09-01Update service specs to avoid instance variablesDouglas Barbosa Alexandre
2016-09-01Fix confidential issues should not be passed to WebhooksDouglas Barbosa Alexandre
2016-08-19Merge branch '4273-slash-commands' into 'master'Robert Speicher
Support slash commands in issues / MR description & comments See merge request !5021
2016-08-17Fix a rubocop violationNick Thomas
2016-08-16DRY up the added update service specs, add two email helpersNick Thomas
2016-08-16Address minor review comments for testsNick Thomas
2016-08-13Enforce permissions in `{Issues,MergeRequests}::{Close,Reopen}Service`Rémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-03 01:58:02 +0300