This release features an experimental rich text HTML editor, display of real names for comments and minor performance improvements to the task editor.
Rich text editor
The task editor was based on the plain-text contents of the task, which was sub-optimal when the task description contained HTML markup. Now there is an experimental setting in the task repository page which allows you to activate the rich text editor.
Be warned that it still has its kinks, and I’m putting this out for feedback rather than for mass consumption. It is expected that the formatting will not yet completely match the one from Mantis and that some features such as highlighting incoming changes and dirty tracking are broken or require a nightly build of Mylyn.
That being said, this is a preview of the editor:
It is built on the excellent HtmlText component which arrived fresh with Mylyn 3.5.0 and features the exact HTML controls which are allowed by Mantis itself. I encourage you to report any bugs you find or improvements you need on the Mylyn-Mantis issue tracker. I hope that in a couple of releases this component will be stable enough to leave the experimental state.
Real names displayed for comments
Whenever available, the real names are displayed for comment authors.
There was one more action which could freeze the task editor while opening, and it has been fixed. It especially affected repositories in offline mode.
This version rounds up a number of small fixes and enhancements.
Better search dialog integration
Searching for an nonexistent issue now pops up an informative dialog, rather than a scary internal error one.
Attachment page enhancements
The attachment description fields is superfluous, and was removed. Comments are now created if specified.
Sub-task creation enhancements
A manual sync was needed to enable the ‘Create Subtask’ action on existing tasks. This requirement has been removed. Also, new sub-tasks have custom fields added before creation.
Previously it was possible for the connector to require a sync when in offline mode, or when rendering the task editor, which resulted in delays in the user interface. This has now been fixed.
The 3.3.0 release focuses on usability issues, aiming to make connector simpler to use and closer to the brower-based MantisBT experience.
Repository dialog improvements
We now recognized when the task repository returns a HTTP redirect, which usually signals that another location should be specified. The user is properly notified, instead of being presented an error dialog.
As you might notice from the above screenshot, we no longer require you to enter the full path to the repository location. Although we support the old setting, we encourage you to enter just the base path to your MantisBT installation.
Moving towards a more automatic style of configuration also means that this is the last version which will support MantisBT installations older than 1.1 . So for the 3.4.0 release we will not support MantisBT 1.0 anymore.
When validating a repository which have know problems which can lead to data loss the user is warned.
Edit task relations for existing tasks
It is now possible to edit relations for tasks which are submitted to the repository. Previously this was only available for unsubmitted tasks.
Much improved progress reporting
The progress dialogs now reflect the correct state when synchronising queries. Previously it would stall at 0%, and not display progress when queries or tasks changes were processed.
Hide ETA and projection when disabled
The ETA and projection fields can be disabled from the MantisBT configuration. If they are, we will not show them anymore.
Version 3.2.0 is a major feature release, comprising of performance enhancements, complete support for localised MantisBT repositories and better support for repository-configured settings.
Refreshing the repository configuration is usually slow due to large number of configuration settings that are retrieved. A first step towards making this faster is to implement refreshing the configuration of a single project only. This feature is now implemented and you can refresh only a single project’s attributes using the corresponding task editor button .
In our tests this cuts down synchronization time from 28 seconds to 6 seconds for a MantisBT installation with 16 projects.
Complete support for localised repositories
We now consider support for localised repositories complete. If it works for an English installation, it should work for any other installation. This includes repository attribute values, mapping priorities and resolutions and task list decorations.
Please note that task attributes will not be properly displayed in certain circumstances, due to a bug in the MantisBT SOAP API – see Troubleshooting: empty attributes in task editor for more details and possible fixes. The good news is that this has already been fixed in MantisBT and will be available in the next stable release.
Better support for repository-configured defaults
All configurable default values for fields ( severity , steps to reproduce etc ) are now preselected when a new task is created. Also, the ‘resolve as’ action preselects the configured status from the repository, rather than defaulting to the current status of the task.
Repository validation enhancements
The unknown error dialog we recently introduces was relatively uncut and appeared in too many circumstances. We know have better detection of predefined error cases and in consequence do not show the dialog that often. In addition, there is a real hyperlink which points to the Mylyn-Mantis troubleshooting page.
We’re confident that this is the best release to date, so download it and give it a spin. If you encounter any issues, let us know through our bugtracker or support forum.
Time has come for another release of the Mylyn connector for MantisBT. I find that these released don’t arrive so often since the connector is solid and has the features that I for one need for day-to-day usage.
Nevertheless, I found the time to remove some issues which have annoyed both me and the users kind enough to report them.
Correct display of incoming changes
I’ve worked hard to correctly display incoming changes in both the task list and the popup notification used by Mylyn. The connector used to display changes from one step behind and this has annoyed me for a long time. No more.
Refer users to the wiki when needed
A lot of support issues have been generated by the fact that incorrectly configured MantisBT repositories work in the web interface, but not with Eclipse. We now suggest visiting the wiki in case an unexpected error appears when validating the repository. The link is Troubleshooting connection problems between MantisBT and Eclipse.
We have finally chased down the last remaining Web-Service related conflict, and we play nice when Web-Service related plugins are installed. Also, HTTP authentication works properly.
Some minor usability issues have also been fixed:
- The query ‘maximum results’ property is now saved;
- The ‘time spent’ is correctly formatted;
- When creating a query for the first time, updating the repository configuration shows a progress dialog, not just a busy cursor.
Please update and report any issues found in our bugtracker or forums.
A few bugs sneaked in the 3.1.1 release – which should’ve been named 3.2.0 due to its new features – so 3.1.2 a small bugfix and stability release is now out.
- All repository dates were incorrectly parsed . This also had the unpleasant side effect of always considering the tasks stale, which slowed operations a lot.
- We now properly retrieve and set the ‘assigned’ status for bugs. This is important for both non-English installations and for projects using custom statuses.
This version is hot on the heels of Mantis 1.2.0 , therefore we build on the latest SOAP features added in that release.
Retrieve tasks using built-in filters
Up till now, retrieving tasks was only possible if you defined filters using the web interface. We now take advantage of recent bug fixes in MantisBT to retrieve the latest project tasks, without defining a project filter.
Due date integration
We now recognize and display the due date field if the repository supports it. Not only that, but the Mantis and Mylyn due dates are kept in sync. Note the due icon and the due date overlay
Basic time tracking integration
It is now possible to add time tracking information, but only if a comment text is added.
The time tracking information for an issue is also presented.
It is not yet possible to see time tracking information for each individual comment or to enter the time tracking in a more friendly format, but I plan to add these in the future.
- The People part has been tweaked to allow an assignee when creating a new issue and to allow un-assignment of an issue.
- The task editor page now has a submit button at the top and has the private section integrated into the Mantis page, instead of a separate one.
- An annoying bug where the plugin would install but fail at startup for older versions of Mylyn has been fixed.
For comments, bugs and support requests, our bug tracker and forums await you.
The Mylyn-Mantis connector 3.1.0 brings new features and stability improvements. The highlight of this release is building on Mylyn’s web services support to bring a more predictable model of interaction with the Mantis repositories.
We now build on the support offered by Mylyn to display a credentials dialog when access is denied for a SOAP operation.
Improved sub-projects display
Sub-projects are now clearly displayed in the new query page.
View state is editable
Up till now the view state was present, but hidden. This release changes it to be visible and editable.
Gracefully handle large number of users
The MantisBT SOAP API does not handle large numbers of users well, and public installations such as the official MantisBT tracker have in excess of 15,000 users. We now populate the users list with the developers and gradually add any users found as issue reporters or note authors when retrieving data.
Resynchronise only when necessary
Up till now, all repository configuration changes happening inside Eclipse triggered a repository configuration refresh. This included changes which did not really affect the repository state, such as recording the last synchronisation timestamp. From now on we re-create the repository state only when a relevant property has changed.
As always, our bug tracker and forums await you.
The Steps to reproduce and Additional info fields are now collapsed if empty. This helps increase the information density when first opening the task editor.
Better support for internationalised Mantis installations
Until this release the connector was reading the task status as a string and looking for the harcoded default values. This broke both internationalised Mantis installations and those with custom workflows.
Now we do the right thing and compare the task status priority with the one defined in the Mantis installation, which means we behave exactly as the web interface does.
Custom field support
The headline for this release is custom fields are now supported. The fields are enabled by default and usable for both new task submissions and editing existing tasks. I’ve also enabled the ETA field to be a drop-down list.
Filtered trees for project selection
Project selection for the new task wizard and new query wizard now use the more elegant filtered trees provided by the Mylyn project.
The new pages should feel much faster than the old ones since reviewing them has uncovered some unfounded assumptions which were costly performance-wise.
I’ve also taken care of a few minor annoyances:
- Replying to comments now properly quotes the origin, instead of (null);
- It is now possible to attach more than one screenshot, and the user-submited names are respected;
- Mantis installations with more exotic access threshold values don’t cause task retrieval failures;
- Repository configuration updates now have a more predictable progress rate;
- Bundle dependencies are now more carefully set, to assist integrators.
As always, our bug tracker and forums await you.