- 12 Aug, 2016 1 commit
-
-
Rémy Coutable authored
Some important things to note: - commands are removed from noteable.description / note.note - commands are translated to params so that they are treated as normal params in noteable Creation services - the logic is not in the models but in the Creation services, which is the right place for advanced logic that has nothing to do with what models should be responsible of! - UI/JS needs to be updated to handle notes which consist of commands only - the `/merge` command is not handled yet Other improvements: - Don't process commands in commit notes and display a flash is note is only commands - Add autocomplete for slash commands - Add description and params to slash command DSL methods - Ensure replying by email with a commands-only note works - Use :subscription_event instead of calling noteable.subscribe - Support :todo_event in IssuableBaseService Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 01 Aug, 2016 1 commit
-
-
zs authored
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 |
-
- 19 Jul, 2016 1 commit
-
-
tiagonbotelho authored
-
- 12 Jul, 2016 2 commits
-
-
Sean McGivern authored
-
Paco Guzman authored
-
- 01 Jul, 2016 1 commit
-
-
Robert Schilling authored
-
- 29 Jun, 2016 1 commit
-
-
Paco Guzman authored
-
- 17 Jun, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
James Lopez authored
-
- 14 Jun, 2016 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Phil Hughes authored
Added a button into the sidebar for issues & merge requests to allow users to manually create todo items Closes #15045
-
- 13 Jun, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 06 Jun, 2016 2 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Thijs Wouters authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 02 Jun, 2016 5 commits
-
-
DJ Mountney authored
-
DJ Mountney authored
Use the project finder in the todos finder to limit todos to just ones within projects you have access to.
-
DJ Mountney authored
-
DJ Mountney authored
-
DJ Mountney authored
By joining the Todos on the project table.
-
- 31 May, 2016 1 commit
-
-
Felipe Artur authored
-
- 25 May, 2016 1 commit
-
-
Stan Hu authored
Closes #17496
-
- 24 May, 2016 2 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
- 17 May, 2016 1 commit
-
-
Sean McGivern authored
When a build fails for a commit, create a todo for the author of the merge request that commit is the HEAD of. If the commit isn't the HEAD commit of any MR, don't do anything. If there already is a todo for that user and MR, don't do anything. Current limitations: - This isn't configurable by project. - The author of a merge request might not be the person who pushed the breaking commit.
-
- 16 May, 2016 1 commit
-
-
Sean McGivern authored
Before: we took the next milestone due across all projects in the search and found issues whose milestone title matched that one. Problems: 1. The milestone could be closed. 2. Different projects have milestones with different schedules. 3. Different projects have milestones with different titles. 4. Different projects can have milestones with different schedules, but the _same_ title. That means we could show issues from a past milestone, or one that's far in the future. After: gather the ID of the next milestone on each project we're looking at, and find issues with those milestone IDs. Problems: 1. For a lot of projects, this can return a lot of IDs. 2. The SQL query has to be different between Postgres and MySQL, because MySQL is much more lenient with HAVING: as well as the columns appearing in GROUP BY or in aggregate clauses, MySQL allows them to appear in the SELECT list (un-aggregated).
-
- 13 May, 2016 1 commit
-
-
Douwe Maan authored
-
- 09 May, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 06 May, 2016 1 commit
-
-
Arinde Eniola authored
-
- 25 Apr, 2016 1 commit
-
-
Stan Hu authored
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/15580
-
- 21 Apr, 2016 1 commit
-
-
Rémy Coutable authored
This is not needed anymore after !3815. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 20 Apr, 2016 7 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Mehmet Beydogan authored
Fix typos on sorting dropdown related to due date Remove constant array and add Structs on Issue to keep due date data to fill options
-
Mehmet Beydogan authored
Add due_date text field to sidebar issue#show Add ability sorting issues by due date ASC and DESC Add ability to filtering issues by No Due Date, Any Due Date, Due to tomorrow, Due in this week options Add handling issue due_date field for MergeRequest Update CHANGELOG Fix ambigous match for issues#show sidebar Fix SCREAMING_SNAKE_CASE offenses for due date contants Add specs for due date sorting and filtering on issues
-
Phil Hughes authored
Fixed issue with no label not working correctly
-
James Lopez authored
-