summaryrefslogtreecommitdiff
path: root/lib/api/issues.rb
Commit message (Collapse)AuthorAgeFilesLines
* Fix API issues sortingfix-api-sortingSean McGivern2016-09-091-3/+9
|
* API: Expose issue#confidentialapi-confidential-issuesRobert Schilling2016-08-311-2/+12
|
* if issue is not valid we revert back to the old labels when updatingtiagonbotelho2016-08-301-9/+2
|
* refactors update issue api request and some minor commentstiagonbotelho2016-08-301-16/+10
|
* adds test to check whether or not an email is sent to label subscribers ↵tiagonbotelho2016-08-301-19/+6
| | | | after creating a new issue through the api
* user is now notified when creating an issue through the apitiagonbotelho2016-08-301-2/+16
|
* Refactored AkismetHelper into AkismetService and cleaned up `Spammable`Patricio Cano2016-08-151-2/+0
| | | | - Refactored SpamCheckService into SpamService
* Refactored spam related code even furtherPatricio Cano2016-08-151-1/+1
| | | | | | | - Removed unnecessary column from `SpamLog` - Moved creation of SpamLogs out of its own service and into SpamCheckService - Simplified code in SpamCheckService. - Moved move spam related code into Spammable concern
* Complete refactor of the `Spammable` concern and tests:Patricio Cano2016-08-151-1/+1
| | | | | | | - Merged `AkismetSubmittable` into `Spammable` - Clean up `SpamCheckService` - Added tests for `Spammable` - Added submit (ham or spam) options to `AkismetHelper`
* Refactor spam validation to a concern that can be easily reused and improve ↵akismet-ui-checkPatricio Cano2016-07-261-7/+5
| | | | legibility in `SpamCheckService`
* Refactor `SpamCheckService` to make it cleaner and clearer.Patricio Cano2016-07-261-4/+6
|
* Submit all issues on public projects to Akismet if enabled.Patricio Cano2016-07-261-5/+3
|
* Submit new issues created via the WebUI by non project members to Akismet ↵Patricio Cano2016-07-261-12/+1
| | | | for spam check.
* API: Expose due_date for issuesapi-isssues-due-dateRobert Schilling2016-07-121-4/+6
|
* gitlab-org/gitlab-ce#17818 - add api call for issues by groupMarc Siegfriedt2016-06-231-0/+35
| | | | | rely only on IssuesFinder docs and changelog
* Fix pseudo n+1 queries with Note and Note Authors in issuables APIsAlejandro Rodríguez2016-06-081-2/+2
| | | | | | | | | This was not a clear cut n+1 query, given that if you're directly subscribed to all issues that the API is returning you never really need to check for the notes. However, if you're subscribed to _all_ of them, then for each issuable you need to go once to `notes`, and once to `users` (for the authors). By preemtively loading notes and authors, at worst you have 1 extra query, and at best you saved 2n extra queries. We also took advantage of this preloading of notes when counting user notes.
* Add API endpoints for un/subscribing from/to a labelAhmad Sherif2016-05-121-38/+1
| | | | Closes #15638
* Use ActionDispatch Remote IP for Akismet checkingStan Hu2016-04-271-2/+2
| | | | | | | | Previously all remote IPs appeared at 127.0.0.1, which made Akismet not very useful. Using the ActionDispatch Remote IP (http://api.rubyonrails.org/classes/ActionDispatch/RemoteIp.html) should provide more reliable results. Closes #16629
* Allow back dating issues on updateMichael Greene2016-04-131-2/+5
|
* Ensure that issues and merge requests are foundRobert Schilling2016-04-131-4/+4
|
* Make subscription API more RESTfulRobert Schilling2016-04-131-23/+6
|
* API: Ability to subscribe and unsubscribe from a merge requestRobert Schilling2016-04-131-2/+2
|
* API: Ability to subscribe and unsubscribe from an issueRobert Schilling2016-04-131-0/+53
|
* Update tests for moving issues via APIRobert Schilling2016-04-131-7/+7
|
* API: Ability to move an issueRobert Schilling2016-04-131-0/+23
|
* API: Expose subscribed? on issuesRobert Schilling2016-04-081-5/+5
|
* Back dating of issues when creating throught the APIZeger-Jan van de Weg2016-03-281-6/+10
|
* Minor improvements on IssuableActionsZeger-Jan van de Weg2016-03-211-6/+2
|
* minor improvements and fixed specsZeger-Jan van de Weg2016-03-191-1/+2
|
* Dry destroy action on issuablesZeger-Jan van de Weg2016-03-191-2/+3
|
* Soft delete issuablesZeger-Jan van de Weg2016-03-191-2/+7
|
* Restrict access to confidential issues through APIDouglas Barbosa Alexandre2016-03-171-1/+2
|
* Refactor spam filtering on issues APIDouglas Barbosa Alexandre2016-02-021-7/+8
|
* Support Akismet spam checking for creation of issues via APIStan Hu2016-02-021-1/+21
| | | | | | | Currently any spam detected by Akismet by non-members via API will be logged in a separate table in the admin page. Closes #5612
* Merge branch 'rename-abilities' into 'master'Dmitriy Zaporozhets2015-06-261-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rename abilities to correspond contoller/model action names write_ was renamed to create_ modify_ was renamed to update_ So now in update action we have next code ``` def create can?(current_user, :create_issue, @issue) end def update can?(current_user, :update_issue, @issue) end ``` See merge request !896
| * Rename abilities to correspond contoller/model action namesrename-abilitiesDmitriy Zaporozhets2015-06-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | write_ was renamed to create_ modify_ was renamed to update_ So now in update action we have next code def create can?(current_user, :create_issue, @issue) end def update can?(current_user, :update_issue, @issue) end Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* | Only people who can manage issue can assign labels to itpermission-improvementsDmitriy Zaporozhets2015-06-261-1/+1
|/ | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Query issues, merge requests and milestones with their IID through APIjubianchi2015-05-021-0/+3
|
* Refactor and improve sorting objects in API for projects, issues and merge ↵Dmitriy Zaporozhets2015-02-051-2/+8
| | | | requests
* Explicitly define ordering in models using default_scopeDmitriy Zaporozhets2015-02-051-2/+0
|
* Filters issues by milestone via APIjubianchi2014-09-261-3/+12
|
* Improve error reporting on users APIjubianchi2014-09-161-2/+2
| | | | | | | | * users (#6878, #3526, #4209): Validation error messages are now exposed through 400 responses, 409 response are sent in case of duplicate email or username * MRs (#5335): 409 responses are sent in case of duplicate merge request (source/target branches), 422 responses are sent when submiting MR fo/from unrelated forks * issues * labels * projects
* Explicit issues order in API. Fixes tests for mysql. Again :)Dmitriy Zaporozhets2014-09-041-1/+3
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Filters issues by labels via APIjubianchi2014-09-041-3/+24
|
* Explicit order of issues in API. Fixes specs for mysql dbDmitriy Zaporozhets2014-09-031-1/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Refactor finders. Prevent circular dependency errorDmitriy Zaporozhets2014-09-021-3/+3
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Filters issues by state via APIjubianchi2014-09-011-4/+23
|
* Improve labels validation and expose error messagesjubianchi2014-08-201-5/+6
|
* Do label validation for issues/merge requests APIRobert Schilling2014-08-141-4/+17
|
* Fix old api compatibility and testsDmitriy Zaporozhets2014-07-301-3/+11
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
View Lorry Controller Status