Release notes: Custom status, new catalog
Posted by Andy Singleton on Thu, Mar 03, 2011 @ 10:22 PM
The biggest change in today's release was custom status. You can get more details here. The major changes are:
- You can go to the Ticket/settings form (near the bottom) to edit the list of status values from the default "new", "accepted", "test", "fixed". In the database I am seeing a lot of signaling statuses like "deploy now".
- We revised the ticket comment form to make it easy to select status and assign the task to a user. By popular demand, we removed some of the workflow restrictions.
- There are some changes to the way we update tickets from commit comments. We no longer have special cases for "closes" and "close" and "fixes" to set "closed" and "fixed" status. To update ticket #4 from a commit comment, you must write "<status> #4", for example, "test #4" or "Fixed #4". It is not case sensitive.
It should be easier to create new spaces with the simplified layout of the "Create a Space" catalog. It features the top five configurations that are used in 90% of new subscriber projects.
The user activity report now shows a list of assigned tickets with total estimated time. I find this very handy. You can get to this report with the little "report" link on the Team list, and you can get a cross-project report from the Users tab in a Portfolio.
We added explanations for space status values on the Portfolio/Spaces page. For example you learn that if you set a space to "Template" status, it gets added to your catalog, and it is called out as an option on the new Create a Space page.
The team ran through 115 tickets in two weeks, even with the extra work of Gerrit reviews. So, we must be getting used to it. There were a lot of small layout fixes for your viewing pleasure.