The original status bar design was a good first step, but it always bothered me that the other attributes got lost in the emphasis on status. Sure you could read the other attributes, but you couldn't tell with just one glance what the real story of the issue was.
The current status bar focuses on the status at the expense of priority, milestone/due date, and the age and last activity of the issue.
After almost 2 years of real world usage, this has become a nuisance that needed to be addressed. Sifter has also evolved significantly during that time, and we've learned a lot about what's important to people. So we now give significant real estate and design attention to the other important elements.
The new status bar design prioritizes the additional relevant attributes that would affect how urgent an issue is.
The goal of the design is to let each attribute stand on its own and intelligently determine how to style itself. If an issue is unassigned, that's a bad thing, and we emphasize it. If it's critical, we need to make sure that doesn't get overlooked. If it's late or due this week, that's important as well. Each element has a range of styling options that emphasize or de-emphasize it's contribution to the overall urgency of the issue.
The new status bar intelligently styles the different attributes based on the urgency of each attribute.
It's still very early, and it's likely this concept will evolve significantly by the time it's implemented, but the direction and concept feel good. It will be much easier to quickly and accurately asses the current state of an issue by taking all of the relevant factors into account.
We built a simple bug and issue tracker named Sifter and we blog about it when we're not working on it. We think it’s a great way to get feedback and keep everyone updated on our status.
Grab our feedWe'll only send emails for significant product announcements, and those happen every couple of months at most. Of course, we won't give away or sell your e-mail address either.