Bugzilla – Full Text Bug Listing
| Summary: | Default target milestone, and milestones order | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | utilisateur_768 | ||||||||
| Component: | Mylyn | Assignee: | Frank Becker <eclipse> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P4 | CC: | eclipse, robert.elves | ||||||||
| Version: | 3.3 | ||||||||||
| Target Milestone: | 3.4 | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows XP | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
utilisateur_768
(In reply to comment #0) > When adding a new bug, the target milestone field is not pre-selected with the > default milstone of bugzilla. The default Milestone is not available in ../config.cgi?ctype=rdf, so we an enhancement in Bugzilla or we can do this with the new XMLRPC API for Bugzilla 3.6. >More over, when using negative sort key for target > milestone, the milestone combo box is not sorted on the sort key order. Could > you sort the target milestone with the sort key value ? If you have an selected product the milestones are displayed in the same order as in ../config.cgi?ctype=rdf (and this should be order by sortkey). If you did not have select an product milestones are shown sorted for the first product and missing Milestones from other products are append at the end. For this case I do not know how we find an order because in two products the same milestone can have two different sortkeys and what value should we use for order? > > Version: 3.6.0 > Build id: I20100429-1549 > Mylyn 3.3.3.v20100330-0100-e3x Thoughts? Created attachment 168645 [details]
mylyn/context/zip
(In reply to comment #1) > > When adding a new bug, the target milestone field is not pre-selected with the > > default milstone of bugzilla. > The default Milestone is not available in ../config.cgi?ctype=rdf, so we an > enhancement in Bugzilla or we can do this with the new XMLRPC API for Bugzilla > 3.6. ok > >More over, when using negative sort key for target > > milestone, the milestone combo box is not sorted on the sort key order. Could > > you sort the target milestone with the sort key value ? > If you have an selected product the milestones are displayed in the same order > as in ../config.cgi?ctype=rdf (and this should be order by sortkey). Well, no. There must be some kind of cache wich not flushed, because the order of the combo box, with a selected product doesn't match the order of config.cgi?ctype=rdf. I did "Update Attributes from Repository" several times on the query wich contain the bug. > If you did not have select an product milestones are shown sorted for the first > product and missing Milestones from other products are append at the end. > For this case I do not know how we find an order because in two products the > same milestone can have two different sortkeys and what value should we use for > order? > > > > Version: 3.6.0 > > Build id: I20100429-1549 > > Mylyn 3.3.3.v20100330-0100-e3x > > Thoughts? In the query form, the milestones are in correct order. Created attachment 169630 [details]
commited patch
This patch contains only the fix for the correct order.
we have the default milestone not in config.cgi so we must wait until XMLRPC is there and get the default milestone from Product.get field internals -> defaultmilestone.
Should we generate an new bug for the XMLRPC stuff and close this one?
Thougths.
Created attachment 169631 [details]
mylyn/context/zip
(In reply to comment #5) > we have the default milestone not in config.cgi so we must wait until XMLRPC is > there and get the default milestone from Product.get field internals -> > defaultmilestone. > > Should we generate an new bug for the XMLRPC stuff and close this one? A new bug with the XMLRPC dependency sounds right Frank. (In reply to comment #5) > Created an attachment (id=169630) > commited patch > > This patch contains only the fix for the correct order. > > we have the default milestone not in config.cgi so we must wait until XMLRPC is > there and get the default milestone from Product.get field internals -> > defaultmilestone. > > Should we generate an new bug for the XMLRPC stuff and close this one? Bug#314744 is now for the XMLRPC part si I close this bug |