Tag Archives: platform

Platform Updates: Move tickets

Today’s push implemented feature request ticket 16, giving the ability to move a ticket from one tracker to another. This is very useful if you have multiple trackers on one project, or have several related projects.

To move a ticket, click the Move link at the top right of your ticket view.

This will give you a select list of your other projects and their trackers,

which will result in your ticket now being in the other tracker.

You can follow other changes to the platform both on the blog and by following the milestones in the platform’s tracker, where you can cote for tickets you’d like to see implemented.

Platform Update: Management of columns in Tracker reporting

We recently rolled out a change to the developer platform which I neglected to tell you about. You now have more control over details displayed in the ticket tracker list view. This issue was tracked in [#4790] if you want to read some of the backstory.

As an end-user, you can modify the columns that are displayed by clicking on the tools icon at the top right of the ticket list. See for example:

This will bring up a dialog where you can select what columns you want to see displayed:

As the project admin, you can make this setting apply for all users of your ticket tracker in the Admin->Tools interface. Click on ‘Field Management’. At the bottom of that page, you’ll see a list of available columns, which you can turn on or off.

You can see what future changes are on the way by perusing the milestones in the platform ticket tracker, and you can influence this by voting on tickets.

Platform update: Menu cleanup

We’ve pushed out another set of updates to the developer platform today, and I wanted to particularly highlight one change.

Projects with large numbers of a particular type of tool – say, many Git repositories, ticket trackers, or mailing lists – have been noticing that their navigation bar was becoming very cluttered, sometimes wrapping a time or two to fit in all of the menu items. In extreme cases – some projects have dozens of code repositories – this made the navigation practically unusable.

In this release, we’ve implemented two tickets, which you can read in more detail in the ticket tracker (#4957, #5479), which address this problem.

The first of these combines multiple items of the same type into a single menu item:

The second one gives you, the project administrator, additional control over this, by letting you define at what point menu items should be collapsed.

You’ll find this option at the bottom of the ‘Tools’ page in your project admin interface.

There’s more in this release, and you can read the full release notes in the push ticket. You can also see what’s coming next by looking at the milestones in the ticket tracker, and vote on individual tickets that you’d like to see happen sooner.

SVN upgraded to 1.7.7

The SVN server has been upgraded to 1.7.7. You can read the SVN 1.7.7 release notes at

While the release notes state that you don’t have to do anything on the client side due to this upgrade, please note:

  • If you’re using HTTP(S) as your checkout protocol, upgrading your client to 1.7, in conjunction with the 1.7 server, will result in a substantial speedup of checkins and updates.
  • There are reports of problems using Jenkins Continuous Integration server with 1.7, using svn:// checkout addresses. You should read this if you are using Jenkins and experience problems. The solution to this is to use the https:// address for your repository, or to upgrade to the latest version of the SVN plugin, which can be done from the admin interface of your Jenkins installation.

Thanks to Björn of the jEdit project for pointing me to useful resources.

Platform updates: side-by-side diffs

A frequently requested feature is the ability to view your diffs side-by-side in the source code viewer. We’re delighted to announce that this feature is now available. You can see this in action in any code browser by selecting the “switch to side-by-side view” link at the top right. For example, take a look at the revision where this feature was added.

As always, you can see what’s up ahead by looking at the milestones in the ticket tracker. Be sure to vote for tickets that you’d like to see worked on soon.