Change Set Integration
Released November 14th, 2005. Send questions to mylar-users@eclipse.org.
Submit feature requests to
Bugzilla.
Items added since Mylar 0.4.1 are
highlighted
|
Change Set Integration |
The active task now corresponds to a Change Set that's managed
by Mylar. All resources in the task's context automatically get included
in this change set, making it possible to synchronize and
commit only those resources. Resources modified that
are not part of the Task Context will appear outside of the Change
Set in the Synchronize view. Note that as with other Change
Sets you need to set the Synchronize view into either Incoming or
Outgoing mode and toggle the "Show Change Sets" button.
|
|
|
|
|
Commit Task Context |
Resources in the Task Context can be committed either by
right-clicking the active task and selecting the Commit Task Context action, or
by right-clicking the Change Set in the Synchronize view. In
both cases the commit message will be populated by the description
and URL of the task (if available). The comment prefix can be
changed in the Task List preferences page.
|
|
|
|
|
Editor management |
When a task is activated, all interesting editors are automatically
opened and the last active node is brought to the top. This
ensures that the Ctrl+E editor list is populated by the the task
context. The option to manage open editors on task activation
and deactivation can be toggled in the Mylar Tasks pull-down.
|
|
|
|
|
Support for Hierarchical Problems Layout |
The
Mylar interest filter can now be applied to the Eclipse 3.2 Hierarchical Layout of the
Problems view. The Flat Layout is recommended when Mylar is
applied, since it helps focus on the markers of interest.
|
|
|
|
|
Task context indication |
If a task is inactive, but
has a context associated with it, the Activate widget appears
lightly filled (i.e. as bug 111722 below).
|
|
|
|
|
Pause and resume context capture |
Pause and resume task context capture using the drop-down menu on
the Task List. This can be useful for quick diversions that
don't warrant a new task. As a reminder of context capture
being paused, the Title of the Mylar Tasks view will change.
|
|
|
|
Proxy settings |
To enable use with firewalls and proxy servers the Bugzilla Client follows proxy settings set in the Install/Update preference page. |
|
|
|
|
Bugzilla 2.20 support |
Bugzilla support has been updated for version 2.20. If you are
switching from Bugzilla 2.18 to 2.20 you will need to update the
existing Bugzilla Queries in your task list. Double click each
query category to edit it, press "Update Options", and then simply
click OK to save the query. Please note that the default
Bugzilla configuration is now 2.20.
|
|
|
|
|
Browser tab for Bugzilla reports |
A new editor tab makes it easy to switch from the Bug Editor to
Browser-based editing. Note that when using the Browser
queries will not automatically refresh after submitting changes on a
bug. You can set the Browser to be the default editor in the
Task List preference page.
|
|
|
|
|
Improved Task List actions and shortcuts |
The Task List popup menu has been improved to be more context
sensitive and to always create items in the category that is
currently in focus. Tooltip behavior has been improved.
Common actions are now keyboard shortcuts: - New Task: ins - Delete: del - Rename: F2 - Copy Description: Ctrl+C
|
|
|
|
|
Links to web reports |
Tasks can be linked to web
pages. For example, if you want a task to correspond to a Wiki
page or to a bug report copy the URL of the report, click the New
Task button on the Task List, and the URL will automatically be
inserted in the Web Link field. If you click Get Description
the title of the page will be inserted into the Description field.
The task will appear with a Web icon decorator, and will
automatically bring up a Task Editor page that loads the web link
when opened.
|
|
|
|
Task context data export |
The Mylar Task List and
related data can be exported, e.g. for backup purposes.
You can now export to an
archive file.
|
|
|
