cubetto's dashboard

cubetto replied on August 05, 2009 01:13 to the idea "Sifter API" in Next Update:

Brilliant. Hopefully we'll be able to integrate it in the QA Loop on our next release : )

cubetto replied on June 27, 2009 23:41 to the idea "Sifter API" in Next Update:

REGARDING EMAIL CONVERSATION AROUND ISSUE

# Need:

-Reply to an email to comment in the conversation
-Receive direct link to attachments

# Nice to have:

-Attachment on email is added to issue
-CC someone in the reply to add to issue's future updates (conly if he has account)

REGARDING INTERACTION WITH OTHER SYSTEMS

# Need:

-Be able to send out a message from Sifter to other system each time an issue is created or updated. For instance an HTTP POST could be sent to a configurable URL with each create or update of an issue, so that a script adds a message or comment in Basecamp.

-Be able to create or update a message in Sifter from other system. For instance, an HTTP POST could be sent to http://demo.sifterapp.com/projects/11... with the authentication header with the API key value (you would just need a way to create this key and update your auth system to accept that user)

A simple response set, like:

200 for success
401 for unauthorized access
500 for failed

would be enough feedback from Sifter

This poses the issue of how to send category, priority and assignee without knowing their codes. I suggest category and priority be sent as a string that matches Case Sensitively and assignee through username. In any case if the data doesn't represent an existent value, leave undefined or set to default as your model constraints.

# Nice to have:

-Be able to update issue status, category, priority or assignee in Sifter from another System

Hope this is useful.

Regards,
n.

cubetto marked one of Garrett Dimon's replies in Next Update as useful. Garrett Dimon replied to the idea "Sifter & Email".

cubetto replied on June 04, 2009 17:58 to the idea "Sifter & Email" in Next Update:

i must disagree with this point of view.

just being able to comment back and forth is really valuable to get people on board that won't log in to the web interface.

on the other side, being able to change, status/priority/etc seems more like toy features that don't matter cause they are usually done by people who do log in to the web interface frequently (typically the project manager or assistant)

regarding autoresponders and signatures, i can share my experience with basecamp's email reply feature:

-signatures usually don't bother cause they are always in the end of the message, so they don't get noisy
-regarding autoresponders, i believe the "reply above this line" mechanic implemented in basecamp effectively removes all issues with them, as most default autoresponders don't include the received message. It Also filters out lots of signatures (at least previous mails signatures for sure, soemtimes not the one of the guy writing the email)
-attachment parsing is not needed

cubetto replied on May 09, 2009 19:45 to the question "Data Export" in Next Update:

this will do the trick : )

cubetto replied on May 09, 2009 19:29 to the question "Data Export" in Next Update:

hi garrett,

we've been asked to deliver the issue list upon delivery of a product. so we now need this to comply with contractual requirements. any ideas when you'll have either an API or an XML/CSV export?

i guess that even an unpaged printable list of the issues could be parsed by us.

cubetto replied on March 30, 2009 13:55 to the idea "Sifter & Email" in Next Update:

I'm sorry to keep pushing for this, but it would be great to have email and/or API. Can we expect to see this in the next three months?

Sifter is getting greater adoption in our company : )

cubetto replied on March 30, 2009 13:51 to the update "Fluid Icon for Sifter" in Next Update:

nice work!

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

we don't need the help desk part, just something to get the bugs in.

we now have the product owner checking an email account and manually inputing the bugs that beta testers report.

it's good to know that your help desk priority isn't high. we'll se how the product shapes up and evaluate again if we need more public exposure for bug fixing. our idea is that people just play with the game, and we develop it, so it doesn't make much sense to get them in the loop for bug fixing. – cubetto, on February 10, 2009 16:47

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

any ETA? its been ok for us so far without emails and API, but when we launch our product late march, the API will become a "Must Have". I love the simplicity but we cannot input user reported bugs by hand. – cubetto, on February 10, 2009 16:31

cubetto replied on January 06, 2009 16:38 to the idea "CC More People About a Bug/Issue" in Next Update:

maybe one way could be to add a "follow" link on issues, so interested people can start following the issue, it isn't completely evident that commenting an issue will CC you into that bug

cubetto shared an idea in Next Update on January 05, 2009 22:49:

CC More People About a Bug/Issue

i'm not sure about this one, but it came up a few times so far:
all bugs have asignees, but we can't CC more people into a bug's status. we thought about creating a few mailing lists for each part of the team, but that needs maintenance, the exact reason why we choose ASP software for this. ultimately, we are looking for something like how you can copy people into messages in basecamp, and how they can remove themselves. i imagine that's a lot, just being able to CC more people on the bug report and have them follow it until the end could probably be enough.

cubetto replied on January 05, 2009 22:45 to the idea "Closed unassigned issues shouldn't count" in Next Update:

that was fast : )

cubetto marked one of Garrett Dimon's replies in Next Update as useful. Garrett Dimon replied to the idea "Closed unassigned issues shouldn't count".

A comment on the idea "Free plan for one project?" in Next Update:

so you get locked out in day 30? i thought it just wouldn't allow for us to add new comments or issues, not lock out... yikes – cubetto, on January 05, 2009 20:18

cubetto marked one of Garrett Dimon's replies in Next Update as useful. Garrett Dimon replied to the idea "Closed unassigned issues shouldn't count".

cubetto replied on January 05, 2009 20:07 to the idea "Closed unassigned issues shouldn't count" in Next Update:

cool, i'll wait for that

cubetto replied on January 05, 2009 20:02 to the idea "Closed unassigned issues shouldn't count" in Next Update:

yep, that should do

cubetto shared an idea in Next Update on January 05, 2009 17:22:

Closed unassigned issues shouldn't count

when you close a bug without it being asigned, it remains in the unasigned list. the best behaviour in my opinion would be that it doesn't count to the unasigned list, cause typically you close an unassigned issue when its dismissed.

cubetto replied on December 30, 2008 16:08 to the idea "Sifter API" in Next Update:

having an API is a must have for us to use the service, specially to integrate bug reports into our publicly available software