Current Articles | RSS Feed RSS Feed

March 30 Release: New Ticket views, Cardwall, Code commenting

Posted by Sergio Romano on Wed, Mar 30, 2011 @ 03:20 PM
 

Tickets (representing issues and tasks) are the core of our workflow.  Today's release includes a big upgrade to the way people see tickets, and an all-new cardwall / scrum board / Kanban board.  These are fun ajax features that you can shape to fit your team.

The Tickets menu features three views: the default Ticket List view, the new Cardwall view, and the Planner view.

Sidebar reporting: The Ticket List now has a sidebar to create and edit reports.  It's faster and more fun than the old "Filters" page.  Plus, it allows you to search text in the selected tickets.  Any user can list and search, and if are an owner, you can save reports for the team.

sidebars resized 600

Cardwall: This is a clean implementation of a cardwall / taskboard / kanban board.  Set your milestone on top, and see what your team is working on.  The columns are defined  with the new custom statuses.

cardwall resized 600

 

Agile Planner:  We improved speed and reliability and added a popup view of the complete ticket history.  We found that many users sort tickets into a particular order, so the default order is now "manual".

planner resized 600

 

Pick your view:  What do you want your team to work on?  If you are using a Kanban process, or you like working from a Scrum board, you can set "Cardwall" as the default landing page for tickets.  You can select "Planner", if you want users to land on your sorted list.  Or, you can stay with the default "Ticket List" view, use the sidebar to configure the exact report that you want your team to work from, and set that report as the default.  Look in the Tickets tab, settings subtab, under "Ticket View Settings".

ticket view settings

Inline comments on changesets

When we released on-demand Gerrit last month, we got requests for a simpler code review system that would be similar to Rietveld.  So, in this release you can write comments directly onto a changeet.  I works for subversion, git and mercurial.

As you read a changeset, click a line number to type a comment.  After you write your comments, "submit" to the comment thread at the bottom.  Or, write your overall impressions into the comment thread.  The comment will appear in the activity stream where the changeset author and other developers can see it and respond to it.

code comment resized 600

 

Portfolio volume discounts and annual packages

We simplified the packaging for Portfolio customers.  You can now get fixed price packages, volume discounts, and annual plans, with two months free.  This provides savings for our best customers, and makes the packages easier to arrange with your accounting person.

In each release we improve Tickets in ways that many users do not notice.  This release lets the light shine, with improvements that every user will appreciate.  We have more on the roadmap.  We also made more than 100 small improvements in other areas.  Thanks for your feedback.

Tags: , , , ,

COMMENTS

I don't see the sidebar reporting, but everything else looks fine.

posted @ Wednesday, March 30, 2011 4:15 PM by Sami Hoda


Have you guys fixed the issue with online [mercurial] repository views (source code, changesets) not being responsive/available to view? (Referring to the incessant message: Sorry, request timed out.) 
 
Just tested, found I'm getting that message *right now*... 
 
I'd rather see stability/speed/bug fixes rather than new features. I value new features, but issues like the above are a bigger hindrance. I've taken to running mercurial's built-in server on my repo clone just because of Assembla's instability...

posted @ Wednesday, March 30, 2011 6:51 PM by Jon L.


How can we export the search result in a csv format?

posted @ Wednesday, March 30, 2011 11:14 PM by Thomas


Awesome news!  
 
The new ficket filer sidebar makes so happy! 
 
The cardwall is so cool! Can't wait to try the new code comments. 
 
You made a good thing better! 
 

posted @ Thursday, March 31, 2011 4:10 AM by Gabriel Radic


I now dream of a Cardwall that can group tickets in columns by Assignee ... or even by Milestones. Mmm.

posted @ Thursday, March 31, 2011 4:13 AM by Gabriel R.


Hi, 
 
update looks great, but it's really annoying that when I go from a report to a ticket, then click the ticket view again I now go back to the default report rather than the report I was just looking at, can you change it back? 
 
Thanks

posted @ Thursday, March 31, 2011 5:13 AM by Seb


I was just about to integrate my kanban app into assembla -- glad you guys integrated it! Keep up the great work on the platform!

posted @ Thursday, March 31, 2011 9:47 AM by Omar Uddin


Your new Tickets folder upgrade is awful. We lost its very important option to customize our Filter criteria by different dates, etc. It was ridiculous decision to take that option out and to state "It's faster and more fun than the old "Filters" page". It's MORE HEADACHE and not fun

posted @ Thursday, March 31, 2011 12:38 PM by Oleg


@Andy Singleton, Maybe just tag the Mercurial feature with "Beta" then, so users know it's not as stable (as opposed to hiding it). 
 
I've been a proponent of Mercurial for the past year, and the only reason I agreed to use Assembla for managing projects for my employer, was due to Mercurial support finally being integrated properly, so you may be losing customers by again hiding it.

posted @ Thursday, March 31, 2011 12:52 PM by Jon L.


Some of my spaces have the new functionality - but the primary one (which also has quite a few custom filters saved) does not have the new sidebar. 
 
However, it does have the updated Cardwall and Planner. 
 
Is there anything I have to do specifically to enable it - or is this just a delay in the roll-out procedure ? 

posted @ Thursday, March 31, 2011 9:32 PM by Gary Menzel


The Planner and Cardwall views are useful for performing sprint planning and to use as a sprint's Scrum board. One issue is that on the Cardwall the Story and its Tasks (Ticket and child Tickets) get separated and mixed among other Stories and Tasks. Is there any way to keep a Story's Tasks grouped together in the Cardwall view?

posted @ Thursday, April 21, 2011 12:19 PM by Blake Buckley


Comments have been closed for this article.

Follow Assembla

twitter facebook youtube linkedin googleplus

Subscribe by Email

Your email: