Get your own customer support community

About me

Recent activity

Subscribe to this feed
  • question

    botskonet asked a question in Next Update on September 25, 2009 03:36:

    botskonet
    Various comments on usability issues
    I've been using sifter for a few weeks for a client and I have some addition feedback.

    - The navigation is not organized in a way I feel is efficient. After traveling through bugs making notes, making changes, the only way I can find my way back to the milestone is to go back to the dashboard and then click the milestone link.

    - When I set view settings for a milestone they don't stick. Next time I visit the milestone they've been reset. I don't want to see closed and resolved tickets in the milestone, and I frequently have to change the status, assignee, etc.

    - The overview/activity/issues links disappear when I'm viewing an issues list. Again, I need to return to the dashboard to access those links again.

    - Links to other issues do not work when enclosed by characters, like parenthesis. (i45) does not get turned into a link.

    I too second the API work, by the way.

    I understand that you're a small business without much time to work on this (at least what you said a year ago when I got to be an early tester), but I'm not comfortable recommending that any of my client use this service because a) it's not what I consider complete and b) with work progressing so slowly it just doesn't seem like I can feel confident about it.

    Thanks!
  • question

    botskonet replied on October 31, 2008 22:45 to the question "not sold yet, what's missing?" in Next Update:

    botskonet
    I didn't realize you were the only person. I'd be curious to learn about what decisions you made regarding processing and managing recurring billing - I have an application launch coming up that will need that and we're still undecided.

    I just personally wouldn't be up for paying so much for the current functionality. I need more power in how bugs are grouped and how they can be assigned to milestones.

    What I find useful is having an easy method of managing which components of the project are affected by the bug, having a way to nest bugs so that one depends on another, etc.

    I use bugzilla for large projects but hate how complicated and outdated it is. Lighthouseapp.com is good tool and currently the best tool for my clients to use.

    I'm always ready to provide feedback and contribute if you need help - I am a web developer (not ruby though).

    http://www.botsko.net

    I think the design could be improved and cleaned up, but that's coming anyway I assume.
    Do you think this answers the question? Mark it as answered
  • question

    botskonet replied on October 31, 2008 22:37 to the question "not sold yet, what's missing?" in Next Update:

    botskonet
    I didn't really mean that it needs a ton of features, but it seems to me that for basic bug tracking, lighthouseapp.com is better suited to handle that right now. I use lighthouseapp.com for some of my clients and I also use bugzilla for larger projects that require a more powerful system.
    Do you think this answers the question? Mark it as answered
  • question

    botskonet asked a question in Next Update on October 31, 2008 22:20:

    botskonet
    not sold yet, what's missing?
    I've been poking around the beta for a little while and am honestly not impressed. I realize it's a beta but I have yet to see anything that gives me more power, flexibility, or ease of use over something like lighthouseapp.com. The UI feels a bit too simple and unpolished at this stage, and it's screaming "ruby on rails". So far, it feels like lighthouse but with less power. Is there something that I'm missing?