not-milestone not functioning correctly
Reported by rick | September 16th, 2008 @ 09:43 AM
"However, the
not-milestonekey isn't working in the search API." -- Arik in #1141
Can you post the full query where not-milestone is
not working? My specs for it all pass, but there may be some cases
where it doesn't work right when used with milestone.
I'll add some more specs for that case, as well as similar keywords
like responsible.
Comments and changes to this ticket
-
Arik Jones September 16th, 2008 @ 09:47 AM
Here is the full query I'm using that isn't working.
not-milestone:"Backlog" state:open not-state:new responsible:me sort:priority -
Arik Jones September 16th, 2008 @ 09:49 AM
Tried this and it didn't fly.
not-milestone:"Backlog" milestone:any state:open not-state:new responsible:me sort:priority -
Arik Jones September 16th, 2008 @ 09:53 AM
- no changes were found...
-
rick September 16th, 2008 @ 06:06 PM
- → State changed from “new” to “open”
Hmm, I think it's some conflict with the
sort:priorityandnot-milestonekeywords.The two 'in a milestone' options are due to
sort:priorityandmilestone:any(priority sorting automatically adds the milestone requirement).I'll look into this further.
-
-
Arik Jones October 1st, 2008 @ 07:59 AM
Sorry to be annoying about this, but what is the ETA on this bug? I'm really missing this search key! :)
-
rick October 7th, 2008 @ 04:20 PM
Sorry, we've had some more urgent issues to work on. I'm finally sitting down to knock this out.
-
-
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Using Lighthouse to track Lighthouse.
Cid Dennis
