Bugzilla – Full Text Bug Listing
| Summary: | Jira query wizard fail to select components and resolution | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> | ||||
| Component: | Mylyn | Assignee: | Eugene Kuleshov <ekuleshov> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | brockj, jason-eclipse | ||||
| Version: | unspecified | Keywords: | helpwanted | ||||
| Target Milestone: | 0.9 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 142783 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Eugene Kuleshov
This bug could be resolved without fixing bug 142783, but doing that could provide the JIRA Connector with the persistence for free. Mik, do you mean that UI for creating search criteria should be unified across all providers? It's tricky, because we want to retain flexibility for each connector without forcing them to re-implement all the search stuff. For now it may be best to simply use Eclipse dialog settings to store that, since we should create common search API before considering creating common UI stuff. I fixed issue with restoring selection in resolution list in a patch for bug 149605 However component selection problem is caused by Jira core services, which seem fail to restore componentFilter in FilterDefinition after Eclipse restart. Brock, can you please take a look at this? *** Bug 169301 has been marked as a duplicate of this bug. *** Actually the only case that didn't work was when component selection has "No Component" and resolution - "Unresolved". I committed fix and tested it manually. Created attachment 56313 [details]
mylar/context/zip
Fixed selection of the assignee |