An error occurred fetching the project authors.
- 30 Sep, 2016 1 commit
-
-
Makoto Scott-Hinkle authored
Updating test value for milestone title Adding API test for title with reserved HTML characters. Updating changelog Adding the MR number for fixing bug #22452. removing duplicate line Updating MR number.
-
- 27 Sep, 2016 1 commit
-
-
Makoto Scott-Hinkle authored
Updating test value for milestone title Adding API test for title with reserved HTML characters. Updating changelog Adding the MR number for fixing bug #22452. removing duplicate line Updating MR number.
-
- 09 Aug, 2016 1 commit
-
-
tiagonbotelho authored
-
- 12 Jul, 2016 1 commit
-
-
Robert Speicher authored
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 16 May, 2016 2 commits
-
-
Sean McGivern authored
Postgres only needs to select a single column, so that can used as a sub-query where `Milestone.upcoming_ids_by_projects` is actually used in `IssuableFinder`. MySQL needs to select the `due_date` column because it's used in the `HAVING` clause, so it has to return an array of IDs.
-
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).
-
- 09 May, 2016 1 commit
-
-
Jeroen van Baarsen authored
In 8278b763 the default behaviour of annotation has changes, which was causing a lot of noise in diffs. We decided in #17382 that it is better to get rid of the whole annotate gem, and instead let people look at schema.rb for the columns in a table. Fixes: #17382
-
- 05 May, 2016 1 commit
-
-
Felipe Artur authored
-
- 17 Mar, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 11 Mar, 2016 1 commit
-
-
Yorick Peterse authored
-
- 07 Mar, 2016 1 commit
-
-
Rubén Dávila authored
-
- 08 Feb, 2016 1 commit
-
-
Zeger-Jan van de Weg authored
Fixes #3903
-
- 09 Dec, 2015 1 commit
-
-
Douwe Maan authored
-
- 19 Oct, 2015 1 commit
-
-
Yorick Peterse authored
This cuts down the time it takes to sort issues of a milestone by about 10x. In the previous setup the code would run a SQL query for every issue that had to be sorted. The new setup instead runs a single SQL query to update all the given issues at once. The attached benchmark used to run at around 60 iterations per second, using the new setup this hovers around 600 iterations per second. Timing wise a request to update a milestone with 40-something issues would take about 760 ms, in the new setup this only takes about 130 ms. Fixes #3066
-
- 03 Oct, 2015 1 commit
-
-
Guilherme Garnier authored
-
- 22 Jun, 2015 1 commit
-
-
Robert Speicher authored
-
- 26 May, 2015 1 commit
-
-
Jonah Bishop authored
The percent_complete method returns a value of 100 when a ZeroDivisionError occurs. That seems like a very strange default for an error case, and results in a bug when a milestone has no corresponding issues (new, empty milestones show 100% completion). This commit changes the rescue value to 0, and subsequently fixes #1656, which reported this problem.
-
- 12 Feb, 2015 1 commit
-
-
Jeroen van Baarsen authored
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 26 Jun, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 09 Apr, 2014 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 21 Aug, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 29 Jul, 2013 1 commit
-
-
Johannes Schleifenbaum authored
-
- 11 Jun, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 May, 2013 1 commit
-
-
Andrey Kumanyaev authored
-
- 15 Mar, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Feb, 2013 4 commits
-
-
Andrew8xx8 authored
-
Andrew8xx8 authored
-
Andrew8xx8 authored
-
Andrew8xx8 authored
-
- 03 Jan, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 19 Nov, 2012 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 13 Nov, 2012 1 commit
-
-
Vincent Bonmalais authored
-
- 09 Oct, 2012 2 commits
-
-
Dmitriy Zaporozhets authored
-
Andrey Kumanyaev authored
-
- 26 Sep, 2012 1 commit
-
-
Nihad Abbasov authored
-
- 05 Sep, 2012 1 commit
-
-
Nihad Abbasov authored
-