Receiving feedback is a time-consuming process. Unfortunately, even the most eloquent and brilliant feature requests aren't guaranteed to make it into an application. Every developer or team has to choose their battles, and while customer requests carry weight, they aren't the only factors. We've put together a list of the four factors we use to decide if a feature makes it into production.

If there's anything about Sifter that I have a love-hate relationship with, it's managing feature requests. On one hand, feature requests and customer feedback are the most valuable ways of understanding where we should steer the ship, and the people that take the time to share are priceless. On the other hand, some people request features with the entitlement of spoiled children who have never heard the word "no" in their lives.

We've got a lot of things going on, and while there haven't been any major updates since the visual refresh and OpenID, the next few months should be big.

One of the most common questions and points of confusion about Sifter is comparing it to a help desk. While there is some overlap between help desks and bug tracking, they have some very important differences.

We recently released an update to Sifter that included search, and despite the deceptively simple name of "search", it's actually a fairly complex feature. I wanted to run through everything involved in getting search up and running. This was written...

This morning we rolled out search and cross-project issue filtering. There's not much more to it than that, but I wanted to give a quick overview of the highlights from the release. Search One of the most challenging aspects of...

Sifter now offers file uploading. We would have loved to have this in there from day one, but we're big believers in iteration. While this is the last major feature release planned before launch, it's just the tip of the...

One of the most difficult aspects of creating a new product is deciding which features are necessary for launch. Leaving out features can make you uncomfortable. However, there's a point where you should be more scared of adding features than leaving them out.