davideuler / gitblit

Automatically exported from code.google.com/p/gitblit
Apache License 2.0
0 stars 0 forks source link

Milestone contains tickets from another milestone #483

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
*Abstract*: Milestones sometimes contain tickets that do not belong to
them.

*Details*: A milestone sometimes contains tickets it should not (both
on the milestones page in the "x open, y closed , z total", and in the
ticket list when displaying all tickets in a milestone).  It seems a
milestone actually contains all tickets belonging to all milestones
with the same first word in its name (before the first space).

*To reproduce*:

- create a milestone "Some milestone"
- create a milestone "Some deadline"
- create a milestone "Other milestone"

- so milestone names all have a space character
- 2 milestones share the same first word
- the 3d milestone has a different first name

- create a ticket in "Some milestone"
- create a ticket in "Other milestone"

-> "Other milestone" will contain 1 ticket (correct)
-> both "Some *" milestones will contain 1 ticket (INCORRECT)

*Version*: Gitblit 1.6.0

Original issue reported on code.google.com by fgeorges on 12 Aug 2014 at 6:00

GoogleCodeExporter commented 9 years ago
I think this is a variation of the same problem reported in issue 469.  The 
Lucene query is tokenizing the milestone term because it isn't properly 
escaped.  If it is the same issue, this is already fixed on master.  If you 
have the time you could build master from source and try it.

Original comment by James.Mo...@gmail.com on 12 Aug 2014 at 6:06

GoogleCodeExporter commented 9 years ago

Original comment by James.Mo...@gmail.com on 12 Aug 2014 at 6:08

GoogleCodeExporter commented 9 years ago
Thank you!  Time is probably what I have less ;-), but I'll try to have a look 
at the build process...

Original comment by fgeorges on 14 Aug 2014 at 2:30

GoogleCodeExporter commented 9 years ago
Don't we all.  Build process is straight-forward - or at least should be.

You'll need a JDK & Ant.

"ant buildGO" will generate the GO build in Windows & unix flavors.
"ant buildWAR" will generate the WAR build.

Original comment by James.Mo...@gmail.com on 14 Aug 2014 at 2:33

GoogleCodeExporter commented 9 years ago
Github mentions Eclipse.  If it is not necessary, I will try then.  Thanks!

Original comment by fgeorges on 14 Aug 2014 at 2:47

GoogleCodeExporter commented 9 years ago
It is not necessary.  A JDK & Ant are the build requirements.  I use Eclipse 
and the project is already setup for Eclipse, that is why it is mentioned.

Original comment by James.Mo...@gmail.com on 14 Aug 2014 at 2:54

GoogleCodeExporter commented 9 years ago
This is definitely the same problem as issue-469 but the first applied for 469 
doesn't cover this case.  I have revised the fix and pushed to master.  It now 
works as expected.

Original comment by James.Mo...@gmail.com on 4 Sep 2014 at 7:19

GoogleCodeExporter commented 9 years ago
v1.6.1 released

Original comment by James.Mo...@gmail.com on 20 Oct 2014 at 9:36