Skip to main content
Release Resolved Community Contributions
May. 14
Meghan Allen made significant improvements to the UI Usage Reporting infrastructure that she has contributed.  Shawn Minto resolved 6 bugs and provided numerous fixes. Boris Pruessmann contributed task editor content assist. Additional bug fixes and enhancements were provided by Benjamin Pasero, Lubox Pochman, Tobias Widmer, Bryan Hunt, Andrew Overholt and Frank Becker.
Mar. 30
Shawn Minto provided numerous bug fixes and enhancements, Meghan Allen improved monitor usage reporting, Fabio Zadrozny improved the Context API for resources, Michael Valenta helped with proxy settings patches and Nathan Hapke set up a Bugzilla 3.0 test server.  Additional bug fixes and enhancements were provided by John Anvik, Wayne Beaton, Juerg Billeter, Leo Dos Santos, Igor Fedorenko, Jean-Michel Lemieux, Benjamin Pasero and Boris Pruessmann.
Feb. 16
Brock Janiczak contributed his JIRA web service wrapper. Meghan Allen contributed monitor improvements and personal activity reporting and Brian de Alwis contributed monitor fixes. Juerg Billeter contributed contributed repository URL drag-and-drop. John Anvik contributed Bugzilla history parsing. Fixes and patches were also provided by Shawn Minto, Hasan Ceylan, Dmitry Stadnik, Hasan Ceylan, Alex Blewitt and Andrew Overholt.

Also see the New & Noteworthy for previous releases

Update Notes
    - We recommend using the Eclipse 3.3M7 release due to the numerous UI improvements (see Eclipse 3.3 only items below).
    - 2.0M2 and later releases will reset your task activity timings (Mylar now uses a new and much more robust timing mechanism).
    - The offline task data cache will be reset, so submit outgoing changes before updating.
    - If upgrading from a 0.x version, first update to Mylar 1.0 and see the corresponding update notes.
    - Trac xml-rpc users: you will need the latest XmlRpcPlugin.


New Task List layout

The Task List layout has been updated to use a custom drawn tree instead of relying on multiple columns in order to provide the following improvements:
  • Support for subtasks (for an example see the Bugzilla section)
  • The icon columns no longer take up a large amount of horizontal space, making more of the Summary visible.  Sort using Sort by in the view menu.
  • The table header and horizontal scrollbar are gone, making 2-3 more tasks visible.
  • The icon scheme has been updated to make incoming indicators easier to pick out, hits more consistent with tasks, and the kind of task appear on the icon (see the Help -> Mylar UI Legend for the updated scheme).  Note in particular that new tasks now have the task icon background and are distinguished by a special incoming indicator.

Note that the incoming overlays can also be configured to use the Synchronize view style icons and left-facing placement via Preferences -> Task List -> Layout.  Please use bug 182772 for feedback or reporting any OS-specific rendering problems.

UI Legend for Connectors

Help -> Mylar UI Legend now displays connector-specific icon contributions. 

Content Assist in Task Editor

The Task Editor now supports content assist.  The proposals include all usernames/emails associated with an "Assigned to" for all bugs in the repository.  The username in the repository credentials is used to highlight your username.

Task tooltips show changes

Task List tooltips now summarize incoming changes, making it easier to scan for changes without opening the task editor.  Note that the popup menu can be used to mark tasks read without opening.

Task Working Sets
3.3 only

Categories and Queries can be added to a Task Working Set.  Switching Task Working Sets makes only the tasks for that working set appear.  This can be useful for those with a large Task List, several non-overlapping projects, different sets of tasks for different venues (e.g. home vs. work).  For 2.0M3 switching working sets is only supported via the working set switcher on the main toolbar.  To switch to see only one working set you need to Ctrl+click that working set, otherwise multiple will be visible.  The create a new Task Working Set use the Edit... button visible below.

Offline Improvements

The offline support has been improved to be more transparent.  Offline data for all tasks, even unread ones, is downloaded in the background, so before going offline all you need to do is run one successful synchronization.  If switching frequently between being connected note that you can toggle background synchronizations via the Synchronize Automatically button in the Task List view menu.  Opening repository tasks is now much faster due to synchronization and offline concurrency improvements.  Any submission errors are now shown on the task editor header (Eclipse 3.3) instead of the Error Log view.  Also note that the History button is now on the toolbar and a Submit buttons has been added as well.

Task Editor Improvements

The performance of repository task opening has improved dramatically because there are no more synchronous trips to the server and all editor pages load lazily.  If editor contents become stale, the header will be updated as below (Eclipse 3.3) or a dialog will show (Eclipse 3.2).  The Synchronize button on the right of the header retrieves the latest contents.  There have also been numerous layout and improvements.

Hyperlinks in Text Editors
(3.3 only)

Hyperlinks are now supported in all text editors.  Modify enablement or behavior via Preferences -> General -> Editors -> Text Editors -> Hyperlinking.

Scheduled Task Presentation

The Task Activity view has been removed and replaced by the Scheduled presentation of the Task List.  When in focused mode this presentation shows only the tasks scheduled for the current workweek.  Since unscheduled query hits will not show, this makes it easier to work without getting distracted by incoming items.  To focus on the workday, use the Go Into action on the day container.  When the focused mode is off, this presentation both past task activity and tasks scheduled for the future.  

Task Editor lifecycle streamlined

The Task Editor no longer closes on submission, and instead shows progress while it synchronizes with the repository. If incoming changes occur while editor is open the refresh will preserve and mark any outgoing changes.  In order to clear outgoing changes use the context menu -> Mark -> Clear Outgoing.  If an editor is opened for a task not in the Task List the Add to Task List action can be used on the editor's context menu. Formatting of the editor has been improved and uses the new form look on Eclipse 3.3.

Hyperlinks in Java Editor
(3.3 only)

References to tasks and bugs in the Java Editor and now hyperlinked consistently with the Task Editor.  The Task Repository must be defined on the corresponding project (set via Project Properties -> Task Repository). References to tasks must be moused over to turn into hyperlinks.

Drag and Drop improvements

To attach files to a repository task them onto the Task Editor from a navigator view or operating system window.  Dragging a URL that corresponds to a task onto the Task List will cause the corresponding task to be created and added to the Task List, if the corresponding repository exists.


Task Repositories

Platform Proxy Settings
(3.3 only)

By default task repositories now use the global platform proxy settings instead of the Platform Update settings.  These can be overridden per-repository.

Max hits settings removed

The "Max hits" setting on task repository queries has been removed since it was too easy to not notice when the max was reached.



Hyperlinks in Annotations and History
(3.3 only)

Team annotations, enabled in the Java editor via popup menu -> Team -> Show Annotation now show hyperlinked references to tasks.  Note that you must press F2 for focus and Ctrl to activate the hyperlink.  Task Hyperlinks are also available in the History view.


Task Context

UI Usage Reports
3.3 only

File -> New -> Other -> Mylar -> UI Usage Report will generate a report of your perspective, view, preference, command and editor usage in Eclipse.  This reporting facility builds on the Mylar Monitor used to study early releases of Mylar and has been extended to upload statistics to the server where they can be accessed by all interested (via the button in the Actions section).  As before, we will be using these statistics as input to evolving and improving the Mylar UI. 

UI Usage Reporting is installable as a separate feature that can be used independently of the rest of Mylar.  Currently it is only available to Eclipse 3.3 users but will be made available to 3.2 users for the next release.  If installed it will ask to run once every three weeks, at which point you will see statistics displayed as below.  We then ask that you share your usage data with the community, via the Submit to button, so that it can help inform Eclipse developers how the UI is being used.  Note that only interaction events that have IDs starting with "org.eclipse" will be uploaded in order to avoid having private ID names made public.  Note that the information gathered also includes interaction information about elements, so to avoid sharing the IDs of private elements make sure to leave on "Obfuscate elements using SHA message digest one-way hash" via the Preferences -> Mylar -> Usage Data page.  More information on how the monitor works can be found in Eclipsepedia.

Context Activation Improvements

Task contexts are now dramatically quicker to activate and provide a perfect restore of the editors that were available when the task was deactivated.  This includes restoring the line numbers and selections of editors closed.  As a result there should be no more need to use the "Pause Capturing Context" action and we are considering removing it (comment on bug 186874 if you still have a use case for it).

Quick Context View

There is now quick view of the task context that  similar to the Ctrl+O quick outline.  Invoke it via Navigate -> Quick Context view or Ctrl+Alt+Shift+RightArrow.  This quick view can be used to show the task context when a navigator view is not visible (e.g. in the Debug perspective) or when the navigator view is not in filtered mode.

Retrieve from Attachments Table

The Retrieve Context action on the attachments table can be used to bypass the Retrieve Context wizard.

Add to Task Context from Synchronize View

The Add to Task Context action can be invoked on change sets or resources that appear in the Synchronize view.  This can be useful when an incoming change set should be reviewed but has no corresponding task context or when outgoing changes have no task context, e.g. if applied from a patch with no context attached.

Task Context editor

The Context tab on the Task Editor provides a preview of the task context contents.  This facility can be used to remove elements and edit their interest, for example, before sharing the context with others. When first opened this view will show all of the elements in the task context that have a corresponding content provider (e.g. Java elements and files). For long-running tasks this can cause a large number of elements that have decayed in interest to show.  The filter slider bar can be used to adjust degree-of-interest threshold to show only the most interesting elements.


Bugzilla Connector

Dependencies show as subtasks

If a bug A is set to "depend on" B, bug B will be shown as a subtask of A.  This supports creating dependent bugs to indicate that the work is not completed until all dependent bugs are done.  Enable this functionality by toggling off Filter Subtasks in the Task List view menu.

Shared Due Dates and Time Tracking

If Time Tracking is enabled on the repository, shared due dates can be scheduled.  When the due date arrives the task will get a small red bell overlay in its upper-right corner.  Personal scheduled for dates can be used independently of due dates.  Tasks with due dates that are not past will have a blue bell overlay instead.  If the time tracking is not enabled, or not supported by the repository, due dates can be used locally as with personal tasks. 

Local user names

If your Bugzilla repository is configured to use local user IDs rather than full email IDs enable the corresponding option on the Task Repository properties page.


JIRA Connector

Attachment support

The JIRA task editor now supports attachments, both for files and for task contexts.  Submission errors are now displayed instead of failing silently.

Hyperlinks in Java Editor
(3.3 only)

If a JIRA repository is set as the task repository on a project hyperlinking will work per task key.

Proxies and Http Auth

The JIRA Connector now supports proxy settings and http auth.  In addition, there have been numerous bug fixes of connectivity and rich editor support.

Hyperlinks in Task Editor

References to JIRA issue keys are now hyperlinked.

JIRA Core Services

The JIRA feature will now install without requiring additional downloads from


Trac Connector

Hyperlinks in Task Editor
(3.3 only)

Trac hyperlinks are now supported in the task editor.

Custom Fields

Trac now supports the selection from a list of pre-defined values for custom fields.



Back to the top