By itself, this is a pretty straightforward release, but it's another one where we're doing a lot behind the scenes to make way for some more exciting stuff. The best way to sum up this release is that we're making it much easier and more efficient to move around within Sifter.
Let's be honest. Bug tracking isn't sexy. It's a tedious but necessary part of ensuring high quality software. When you're working at the scale of companies like Apple, Microsoft, Oracle, or one of the other huge software companies, it can go to another level entirely. Regardless of the context, there's a human side of the process that is frequently taken for granted.
Priorities are tricky. They can be subtly complex or wildly simple. They can factor in severity, effort, value, or any variety of facets. They can be expressed in words, due dates, or relative values. The approaches are countless, and the advantages and disadvantages of each are just as plentiful.
Have you ever looked at something later in a project and thought "Why did we do it that way?" or "What did we do to fix that problem?" By ensuring you and your team always enter detailed resolutions, you can make it easier on yourselves down the road.
While only available to admins, one of the great features of Sifter is the ability to move issues between projects if they are mis-filed or otherwise simply need to be associated with a different project.
Anytime you setup a filter in Sifter, you can use your favorite bookmarking tool or your browser to add it to a list for later. Whether it's a keyword search, a certain sort and filter combination, or just a list of the issues you want to work on this week, it's only a bookmark away from being easily accessible in the future.
Sifter's identity is changing. Until recently, it's generally been an afterhought, but that's starting to change an evolve as we get a clearer picture of what we want to be when we grow up. Combined with the increasing number contexts within which an identity lives these days, we decided it was time to update our identity.
We've spent the last few months working on infrastructure, and, on the surface, it probably looks like we haven't done much at all with Sifter. Really, we've been investing in key parts of Sifter that are necessary but more or less invisible to customers. Rest assured, we're wrapping that up, and we're wildly excited about what's next.
Bug and issue tracking is different for every team. It depends on the size of your team, the structure of your organization, division of responsibilities, and priorities. We see lots of common myths, assumptions, and hangups in feature requests. Like anything else, even a great tool can't help if you focus on the wrong things.
Software development has come a long ways. It's no longer just the realm of programmers. We have usability experts, visual designers, interaction designers, information architects, business people, and more. With today's smaller and more integrated teams, non-technical people can't be treated as second-class citizens that aren't knowledgeable enough to join the conversation.
Follow the account that's right for you.
We're fast. Ask us and we'll usually get back to you in under an hour.