delta/gitlab/gitlab-ce.git/spec/features/issues_spec.rb, branch docs/issue-closing-pattern

Reordered dropdown options

2016-09-07T14:12:03+00:00

Rearranged datetime created line

Added `avatar_class` option to `link_to_member` so it can be hidden

Made snippet title font heavier

Added file title  bar

Hidden unneeded info from xs screens

Added visibility icon

Reveal file-actions on xs screens

Added comments icon to snippets list items

Refactored no-comments declaration into framework stylesheet

Final touch ups

Fixed snippets_spec

Revert the revert of Optimistic Locking

2016-08-22T15:43:13+00:00

Disable “issue by email” feature until it uses a different token

2016-08-20T00:49:12+00:00

fixes part1 of files to start using active tense

2016-08-09T14:06:23+00:00

State specific default sort order for issuables

2016-08-01T09:28:56+00:00

Provide more sensible default sort order for issues and merge requests
based on the following table:

| type           | state  | default sort order |
|----------------|--------|--------------------|
| issues         | open   | last created       |
| issues         | closed | last updated       |
| issues         | all    | last created       |
| merge requests | open   | last created       |
| merge requests | merged | last updated       |
| merge requests | closed | last updated       |
| merge requests | all    | last created       |

Test both for having existing issues or not

2016-07-27T10:07:24+00:00

Update the description a bit

2016-07-26T11:01:58+00:00

Test if we're showing the modal and has the right email

2016-07-26T11:00:36+00:00

Revert "Merge branch 'gl-dropdown-issuable-form' into 'master'"

2016-07-15T23:46:29+00:00

This reverts merge request !4970

Merge branch 'revert-lock-for-issuable' into 'master'

2016-07-15T18:29:50+00:00


Revert "Optimistic locking for Issue and Merge Requests"

The migration to add `lock_version` in !5146 to every issue and merge request takes too long on GitLab.com since it has to add a default value of 0 to every row. Unfortunately, Rails 4.2 doesn't work properly if the value is left as `nil`; anything using optimistic locking cannot be edited. 

This bug was fixed in Rails 5.0 via this commit: https://github.com/rails/rails/commit/13772bfa49325a8dc26410d2dcb555665a320f92. I suggest we revert this change for now, and when we upgrade to Rails 5.0 we can reintroduce this feature.

See merge request !5245