| Summary: | [context] find referencing tasks/contexts for an element | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mik Kersten <mik.kersten> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | marc.eaddy |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
| Whiteboard: | |||
|
Description
Mik Kersten
Any plans to work on this one? Yes, this needs to be part of the next rev of the context model, which will provide both this search UI, and the ability to maintain handles in inactive contexts. But it is a big task, so not sure yet if it will make 0.7. This feature would be very useful for determing all the bugs that are associated with an element. For example, you can determine which classes have the most bugs. With a little more work you can determine which "features" or "requirements" have the most bugs (this is what I'm doing). Need to postpone due to 2.0 focus on APIs and rename overhead. Please vote if interested in this feature. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |