summaryrefslogtreecommitdiff
path: root/spec/features/issues/create_issue_for_discussions_in_merge_request_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Replace '.team << [user, role]' with 'add_role(user)' in specs36782-replace-team-user-role-with-add_role-user-in-specsblackst0ne2017-12-221-2/+2
|
* Replaces `tag: true` into `:tag` in the specsJacopo2017-10-071-1/+1
| | | | | | Replaces all the explicit include metadata syntax in the specs (tag: true) into the implicit one (:tag). Added a cop to prevent future errors and handle autocorrection.
* Use `empty_project` where possible in spec/features/issuesRobert Speicher2017-07-271-1/+1
|
* Remove superfluous type defs in specsKeifer Furzland2017-07-271-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Auto-correct ProjectPathHelper violationsRobert Speicher2017-07-061-9/+9
|
* Change gitlab_sign_in to sign_in where possibleRobert Speicher2017-06-291-2/+2
|
* Change `login_as` uses to `gitlab_sign_in`Robert Speicher2017-06-191-2/+2
|
* fix Resolved Discussions counter wrapping to next lineSimon Knox2017-05-131-1/+1
| | | | | change all .nav-links to use flex place Resolve Discussions above tabs on small screens, and to the right on large
* Merge request widget redesignFatih Acet2017-05-091-4/+4
|
* Add option to start a new discussion on an MRDouwe Maan2017-04-051-1/+1
|
* Rename variableBob Van Landuyt2017-03-131-6/+6
| | | | | merge_request_for_resolving_discussions -> merge_request_to_resolve_discussions_of
* Show correct message when user cannot resolve discussionsBob Van Landuyt2017-03-131-44/+58
|
* Add a button to delegate all discussions in a merge requestBob Van Landuyt2017-03-131-20/+45
|
* Delegate a single discussion to a new issueBob Van Landuyt2017-03-131-24/+2
| | | | | | 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.
* Feature: delegate all open discussions to IssueBob Van Landuyt2016-12-051-0/+76
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.