Oriact Blog

Dear Users,

We've just updated the servers with Origo's new version, 2010.3. By far the largest change of this release is the issue tracker: large parts of the the main overview page were rewritten to support a brand new feature - custom filter categories. But there's a slew of other new features, too! Here's an overview over all of them

Custom Categories

Until now, the issue tracker's filtering capabilities were quite limited: you're provided with a fixed set of six filters, the "Tags" containing most of the tags one assigned to the issues. But we now have changed this to be much more flexible! You may categorize issue tags by using a special delimiter, "::" (two colons). Each used prefix will cause a separate filter to appear on the issue overview page. So by using e.g. "priority::high" and "priority::low" in your issues will result in a new filter, which you can direct use for searching through your issues.

We also added the possibility for project owners to order and hide the filters, so you can rearrange them to suit your needs. Just click the "Customize Filters" link, and drag and drop the filters around, or click the "hide" icon to remove them from public view.

Horizontal Layout

We've rearranged some of the input fields in the issue pages. It now puts some of the inputs side-by-side, resulting in a broader page, and thus eliminating some of the necessary scrolling to get to the main "Description" field.

Take Button

The "Assigned To" input field now sports a "Take" button - a useful little shortcut when assigning issues to oneself!

Code Highlighting

Patrick enabled a whole lot of new languages in the code highlighting engine for you to enjoy more colorful code :) Check the list of supported languages right below the text input field when creating new or editing existing content.

Striked-through issue links

Another little useful helper: each issue that you link to using the [[issue:123]] shortcut will decorated with a strikethrough if the referenced issue is closed. This comes in very handy on lists of issues, where you can see the state of an issue at a glance!

Pagination of Reported Issues

The Reported Issues page was overhauled and now displays your issues in a paginated table, thus resolving the display errors we've had for users with a lot of reported issues.

New Setting "rss show unread"

You can now control the contents of your dashboard RSS feeds: should it display all work items (and let your RSS reader handle which ones you already read), or only new ones that you haven't seen before? Uncheck the box to restrict the feed to unread items only (note: this setting may take a while to show its effect, as the feeds are cached on the server).

New Setting "issues per page"

There's a new setting where you can choose how many issues you want to display on a single page of the issue overview. The "Reported Issues" page will use the same setting.

Configurable project frontpage

Project owners now have the option to change the project's landing page, e.g. to directly show the issue-tracker when navigating to the project. The setting can be found in the Navigation section of the project settings.

Other Changes

Of course there are further changes and bug fixes in this release, amongst them

• Show diff in work item notifications for edited comments
• Lift restriction on uploadable files (don't check file extensions)
• API changes

  The user.list_reported_issues API call was changed so it can be used with pagination. Consult the changelog for details.

• Code blocks now show line-numbers
• Highlight changes to special tags
• SVN Links in commit mails wrong
• Improve sign in message
• Refrain from creating Issue-Nodes when an error in the back end occurs (prevents "Zero Issues")

As always, the more technical details of this update and its list of bug-fixes can be viewed in Origo's changelog.