Posts for the month of February 2008

Login, Profile and Project Membership changes

This week we have made some changes to how user registration and applications for project membership works.

As before, the minimum required to create a login is a valid e-mail address. However, very often the needs of project owners extend beyond that in order to evaluate and grant permission, and to get in touch with project members if needed.

Based on this we have made a setting in a new 'Memberships' admin page:

Screenshot of setting to 'require profile'.

The setting is optional for each project, and what is needed will be clearly stated on the application form. When granted access to such a project, your basic profile information (name, company and contact details) will be available to the owners of that project.

We have made a number of improvements to the registration and application forms when implementing this, and hopefully getting access to projects will be even easier than before.

  • Posted: 2008-02-19 19:36 (Updated: 2008-02-21 01:03)
  • Author: simon
  • Categories: news
  • Comments (0)

Introducing InterWiki

Many of you (if not all of you) have relations to other systems while developing and maintaining your CodeResort project. Tickets, Wiki pages, Subversion log messages and so on fills up with full links to external systems.

It may be that you use some other bug tracker, or perhaps reference pages on test or production systems that showcase a bug. It could be anything. What makes these links a bit difficult is that they often are:

  • Difficult to read and reference
  • Don't get updated when a system moves from one address to another
  • Not pretty

InterWiki makes it possible to build your own link syntax. In the same way you can link to a wiki:WikiStart (wiki page) or ticket:42 (ticket), you can now make a link that looks and behaves just as you need it.

Say for instance that you have a test and production setup and your project also deals with bugs on pages and content planning. If the content pages are numbered, how about referencing them as prod:525 or test:233?

If you use some other bug tracker with your project, how about just typing bug:123 and have a full external link rendered?

Or, if your project uses modules from another project, such as the epicode project that you need to reference, how about typing epicode:ticket:42 to make a link? Even display this link as descriptive text by using this pattern: [epicode:ticket:42 related issue]

Want to know how? Read up on the HelpUser/InterWiki help page - you'll find all you need to get started.

Saving Custom Queries as Reports

Thought I'd drop a note on yet another new feature that is easy to miss - a very useful feature for anyone using the Ticket system.

Projects contain two types of ticket listings. The listed Reports used to be SQL only. Anyone looked at the SQL or tried to modify or make new SQL-based reports? Not as easy as anyone would have liked.

Custom Query on the other hand is great for picking the criteria of the selection, selecting grouping, ordering and also what columns you would like to display. However, unless you set them up as [query:] links or inline using the [[TicketQuery]] macro, they were temporary.

No longer. This button is now available on Custom Query pages:

'Save Query' button.

Saving a query as a report makes it appear on the 'View Tickets' front page, and allows you to link to it using the report syntax: {10} or report:10

Much nicer don't you think?