Garrett Dimon's dashboard

Garrett Dimon made a comment on "Sifter & Email", but it was removed. see the change log

Garrett Dimon made a comment on "Sifter & Email", but it was removed. see the change log

A comment on the idea "Sifter & Email" in Next Update:

We'd certainly like to add it in the future, but we don't have a specific ETA. Currently we're focusing all of our development effort on the API. – Garrett Dimon, on November 27, 2009 16:55

Garrett Dimon set one of Garrett Dimon's replies as an official response to "Sifter is getting slower" in Next Update

Garrett Dimon replied on November 24, 2009 18:48 to the problem "Sifter is getting slower" in Next Update:

We're definitely already looking into that. I noticed it late last week and have been spending some time to figure out where the problem is. Thanks for the heads up, though. I'll keep you posted.

Garrett Dimon replied on November 24, 2009 18:39 to the problem "Sifter is getting slower" in Next Update:

Can you be more specific? Is it a specific page or a task that feels slow? Is it the app in general? We did have some minor performance problems on a couple of pages that should be sorted out now.

I'm also in the process of evaluating a couple of the more database intensive pages, the dashboard for example, to do some optimization there as well.

Garrett Dimon set one of Garrett Dimon's replies as an official response to "Issues by milestone, customisable priorities" in Next Update

Garrett Dimon replied on November 18, 2009 18:44 to the idea "Issues by milestone, customisable priorities" in Next Update:

Regarding the first request, that's already in there. Under the "Project Settings" tab of each project, you can create and configure milestones. Then, you can use them just like categories and even filter by them within the project's issue listing.

The second one is unlikely for the foreseeable future.

Also, in the future, it helps if you split the ideas into two separate topics so that it's easier for other people to vote for a feature or provide their own thoughts on the topic. For instance, I labeled this request "Implemented" because milestones are implemented, but the second requested feature isn't implemented, so it kind of gets lost. Whereas, if it was its own topic, it's possible that lots of people might be wanting this and be able to add their thoughts and vote it up.

A comment on the idea "Quick Project Switching" in Next Update:

We'll keep this in mind, but I believe our planned interface updates will help alleviate the extra click.

Search is really scoped to the context of the active project, so automatically switching or including all projects isn't really expected behavior, and to a degree it's counter-intuitive. However, since issue numbers are unique across an account, they fall into a grey area. The short answer is that we'll need to think about it some more. Thanks for the suggestion, though. – Garrett Dimon, on November 18, 2009 18:37

A comment on the idea "Import from other systems?" in Next Update:

It's something that we might consider integrating with someday, but until our API is robust enough for other issue tracking options to integrate directly with us for getting the data out of Sifter, it's unlikely that we'll do any direct integration. Even then, we still may not hook in directly like that. – Garrett Dimon, on November 18, 2009 18:30

Garrett Dimon set one of Garrett Dimon's replies as an official response to "What Features Are You Working On For the Next Release?" in Next Update

Garrett Dimon set one of Garrett Dimon's replies as an official response to "TenderApp Integration for Sifter" in Next Update

Garrett Dimon replied on October 30, 2009 16:54 to the question "TenderApp Integration for Sifter" in Next Update:

We need to get our own API working first. :)

Long-term, though, it's much more likely that we would add a help desk piece to Sifter so that it's all one product and seamlessly integrated. We see public projects and help desk functionality as being a very reasonable and likely extension for Sifter.

That doesn't preclude Tender integration at some point, but it's likely that we'd focus on building or own or extending Sifter before integrating with another tool.

Garrett Dimon set one of Garrett Dimon's replies as an official response to "Incorrect Matching Issues Count" in Next Update

Garrett Dimon replied on October 29, 2009 21:09 to the problem "Incorrect Matching Issues Count" in Next Update:

This is fixed now. Let me know if there's anything else that we can help with.

Garrett Dimon replied on October 29, 2009 19:08 to the problem "Incorrect Matching Issues Count" in Next Update:

I'll take a look at that and get it fixed here shortly.

A comment on the idea "Source control integration" in Next Update:

We don't have a date or even a specific timeline. All we can really tell you at this point is that it will be out when it's out. – Garrett Dimon, on October 29, 2009 14:48

A comment on the idea "Source control integration" in Next Update:

We're all over it. The API is the gating factor, and that's where we're focusing 110% of our development time right now. – Garrett Dimon, on October 29, 2009 13:06

A comment on the idea "Sifter API" in Next Update:

I completely understand, and nobody would love to have an API out tomorrow more than me. I assure you that I'm 100% focused on the API at this point and giving it every ounce of time that I have.

Hopefully it will have been worth the wait when it arrives. – Garrett Dimon, on October 25, 2009 07:16

Garrett Dimon set one of Garrett Dimon's replies as an official response to "Sifter API" in Next Update