Hi, The mailing list being somewhat low in volume and not linked to the closed-circle ticketing system at https://issues.apache.org/bloodhound/, I hereby wanted to mention some issues I found with milestones and their due dates. Please tell me if I'm off limits here, and I'll look somewhere else.
All this pertains to v0.8, freshly moved from Trac to BH. Milestone due date in queries: Probably the only question and not a bug report here: How can I use or even see the milestone due date in a query? I have found no way of doing so. This is a major field to me. Milestone and cache: Yes, I'm one of those affected by #681 Whenever one changes a component or a milestone, one MUST restart apache otherwise the changes are not or not well taken into account. Milestone due date entry: Haven't found a ticket on this. Tested on chrome, safari and Firefox. It is impossible to select the first week of the month when entering a due date, as that week is hidden behind the product selection bar. Milestones on dashboard: #686. To me this is not major, but at least critical. How can the default dashboard be anywhere near what business users or even developers would like to see? Issues with Custom dashboard with milestones: * I had to replace the dashboard. I tried to add a report to the dashboard, but for that I had to enable the report module in trac.ini (although reports are possible elsewhere without that setting). That however broke BH completely. So now I have set up a kind of wiki page in place of the dashboard. * When tweaking the query on the dashboard (adding milestones), I found that on the default, 'no product' dashboard, milestones do not even exist and therefor that query has no use at all. Sorting in queries: #654. Sorting is completely broken. I second urgent repairs on this. I have to revert to grouping (and a lot of time lost in meetings when bickering of what ticket is the next on the list, as everybody has a different display order) to make queries slightly usable. I strongly advise you to reconsider your classification of Reports as 'deprecated'. They at least work. <rant> Having moved from Trac to BH, sure BH is nicer looking, but I have lost in productivity due to the large number of bugs in BH. I am seriously thinking of going back or even jumping to Jira. As it is now, I would NOT consider this product production ready. Cmon guys, I'm really disappointed. And then seeing that all of the tickets I've referred to were moved to '0.x', that is blatant disregard for users. </rant> Kind regards, Hans BOOT
