Attachment 31781 Details for Bug 120952 – Brock's requirements for generic issue tracker support

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Brock's requirements for generic issue tracker support

requirements.txt (text/plain), 4.45 KB, created by Mik Kersten

on 2005-12-14 15:35:29 EST

(hide)

Description:

Filename:

MIME Type:

Creator: Mik Kersten

Created: 2005-12-14 15:35:29 EST

Size: 4.45 KB

patch

obsolete

>P1 Centralised view for creating and browsing issue trackers
>This view will be much like the CVS repository browser, but it will allow any issue provider to add an issue server instance.
>
>There will be two common actions:
>- Add server wizard
>- remove instance
>
>New providers will be registered using extension points.  The provider will need to register a new server wizard as well as a structure provider for the view.  It is expected that the issue provider will expose some way of performing a query against the server.
>
>This view could be based on the common navigator
>
>P1 Issue search results view
>This view will hold the results of an issue query.  Most server specific actions will be performed from this view.  The view will be capable of storing the results of multiple searches and the user will be able to switch between the results.  Issue providers will be responsible for creating the pages in this view as well as registering actions.
>
>Actions may be a problem for this view.  Each provider is going to need its own actions and there will be few if any in common.  Should probably see how the search view does this.
>
>P2 Issues perspective
>We should consider adding a perspective that contains the issue browser view and the query result view and an editor section.
>
>
>P2 Associate a repository to project
>Much of the richer integration requires knowledge of which repository is associated with a resource.
>
>P2 Automatic creation and assocciation of an issue provider
>To make the creation of issue tracker instances easier it would be nice ot have a function that will create an issue tracker instance as well as associate it with a project as soon as it is checked out/imported into the workspace.  For this to work, the location and type of the repository must be stored in the project somewhere.  The project preference scope would be a perfect spot for this.  Credentials will not be stored in the preferences, they will have to come from the workspace keyring.
>
>P3 Common query facility
>Investigate what would be required to have a generic query and result object.  Would there be a benefit to doing it this way?
>
>P3 Integrate/push down Mylar task view
>When working with an issue list it is quite common to have a personal list of issues that you are working on.  It should also be possible to create 'offline' issues in this view that can be latr created in the tracker.  It would alos be nice if it could periodically query the server and inform the user if there were any changes to the list of issues.
>
>Being able to enable and disable the current issue would be of use as the issue tracker could be notified of the work stared and work stoped events.  The current issue could also be used during checkout to populate the bug reference
>
>P4 Pre-populate commit message with issue details
>When commiting a change to version control it is helpful if a bug reference is included so the change can be linked back to the orginal issue or issues.  To help the user a template could be provided that would include an appropriate bug reference as well as an optional description.
>
>P4 Resolve issue on commit
>A change is usually commited as a direct result of resolving an issue.  It would be nice if the user could resolve one or more issues at the same time as they commit a change to version control.  The commit wizard lives at teh CVS level, so this would require a cahnge in Team to support.  VCS providers would also need to be updated.
>
>P5 Hyperlinking to Issues in text editors
>Add a hyperlink detector for text files that will allow the user to ctrl+click to view a bug from a text file.  The format of the bug reference will be provider specific.  The hyperlink detector will have to query the issue provider that is attached to the resource to get the refernce format and the open issue action
>
>P5 Hyperlinking from a CVS/SVN revision to one or more issues
>Commits to a version control system usually relate to one or more issues in an issue tracking system.  It would be of great value to be able to open the associated issue from a revision.  This will be hard as there is no way to know which issue tracker should be used to match the bug reference.
>
>P5 Hyperlinking from a remote resource to an issue
>It would be nice to be able to open an issue from a remote resource (CVS revision).  For this to work there needs to be a way to determine what issue tracker is assocaited with the resource.  THis may require traversing the remote resource heirarchy to get the project preferences.

Actions: View

Attachments on bug 120952: 31781