Milestone contains tickets from another milestone

[gitblit]

Originally reported on Google Code with ID 483

*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

Reported by fgeorges on 2014-08-12 18:00:39

[gitblit]

I think this is a variation of the same problem reported in issue 765.  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.

Reported by James.Moger on 2014-08-12 18:06:42

[gitblit]

Reported by James.Moger on 2014-08-12 18:08:17

• Status changed: Accepted
• Labels added: Milestone-1.6.1

[gitblit]

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

Reported by fgeorges on 2014-08-14 14:30:29

[gitblit]

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.

Reported by James.Moger on 2014-08-14 14:33:33

[gitblit]

Github mentions Eclipse.  If it is not necessary, I will try then.  Thanks!

Reported by fgeorges on 2014-08-14 14:47:43

[gitblit]

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.

Reported by James.Moger on 2014-08-14 14:54:04

[gitblit]

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.

Reported by James.Moger on 2014-09-04 19:19:05

• Status changed: Queued

[gitblit]

v1.6.1 released

Reported by James.Moger on 2014-10-20 21:36:03

• Status changed: Done