- 23 11月, 2016 1 次提交
-
-
由 Valery Sizov 提交于
-
- 30 9月, 2016 1 次提交
-
-
由 Makoto Scott-Hinkle 提交于
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 9月, 2016 1 次提交
-
-
由 Makoto Scott-Hinkle 提交于
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 8月, 2016 1 次提交
-
-
由 tiagonbotelho 提交于
-
- 12 7月, 2016 1 次提交
-
-
由 Robert Speicher 提交于
-
- 03 6月, 2016 2 次提交
-
-
由 James Lopez 提交于
This reverts commit 3e991230.
-
由 James Lopez 提交于
# Conflicts: # app/models/project.rb
-
- 16 5月, 2016 2 次提交
-
-
由 Sean McGivern 提交于
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 提交于
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).
-
- 10 5月, 2016 1 次提交
-
-
由 Jeroen van Baarsen 提交于
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
-
- 06 5月, 2016 1 次提交
-
-
由 Felipe Artur 提交于
-
- 18 3月, 2016 1 次提交
-
-
- 12 3月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
-
- 07 3月, 2016 1 次提交
-
-
由 Rubén Dávila 提交于
-
- 08 2月, 2016 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Fixes #3903
-
- 09 12月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 19 10月, 2015 1 次提交
-
-
由 Yorick Peterse 提交于
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 10月, 2015 1 次提交
-
-
由 Guilherme Garnier 提交于
-
- 22 6月, 2015 1 次提交
-
-
由 Robert Speicher 提交于
-
- 27 5月, 2015 1 次提交
-
-
由 Jonah Bishop 提交于
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.
-
- 13 2月, 2015 1 次提交
-
-
由 Jeroen van Baarsen 提交于
Signed-off-by: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 27 6月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 09 4月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 21 8月, 2013 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
- 29 7月, 2013 1 次提交
-
-
由 Johannes Schleifenbaum 提交于
-
- 11 6月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 05 5月, 2013 1 次提交
-
-
由 Andrey Kumanyaev 提交于
-
- 15 3月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 18 2月, 2013 4 次提交
-
-
由 Andrew8xx8 提交于
-
由 Andrew8xx8 提交于
-
由 Andrew8xx8 提交于
-
由 Andrew8xx8 提交于
-
- 04 1月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 03 1月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 20 11月, 2012 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 13 11月, 2012 1 次提交
-
-
由 Vincent Bonmalais 提交于
-
- 09 10月, 2012 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Andrey Kumanyaev 提交于
-
- 27 9月, 2012 1 次提交
-
-
由 Nihad Abbasov 提交于
-