This release targets the unification of internal handling of filters, reports and web queries. Yet, there is one new feature and a lot of cosmetic changes.
BUGtrack Professional Edition now allows customization of the resolution status list. New status can be added, existing ones can be renamed, reordered or removed.
Then, we revisited title editing again. When opening new issue, title is now placed inside of the entry form, unifying user interface, and the focus goes to the title input box. Also, error reporting becomes more consistent this way.
Next, there is no need to edit bug to change the title – it is now editable in place. Title block now issues edit icon which brings up an editor in-place; of course you have to have edit permissions. Changes are saved immediately, when you click on the Save icon or press Enter key. And you may cancel the editing by clicking Undo icon or pressing Escape key.
We've improved the way attachments with long file names are displayed in the conversation thread. The filename is now cut to two lines, to see the file name in full, hover the mouse cursor over the file's icon or thumbnail.
Estimates are now accept the values with the precision up to minute. The input boxes are accepting a old formats as well as new ones, such as
|1.5d||one day, four hours (assuming eight hours working day)|
|1d 4.2h||one day, four hours and 12 minutes|
|1d 4h 12m||one day, four hours and 12 minutes|
|4h 12m||four hours and 12 minutes|
|4:12||four hours and 12 minutes|
If the string you enter contains minutes, no fractional parts of hours and days are allowed. On output, BUGtrack tries to present the value with fractional parts of hours when possible – 1:30 will be displayed as 1.5 hrs, while 1:20 will be displayed as 1 hr 20 mins.
Please note that the number reported through the web query XML in the estimate's value attribute is now also reported in minutes, comparing to tenth of hours old version reports – in other words, to get the value in old format you should divide new value by 6. If you ever rely on this, please update your code or XSL transformations.