Get your own customer support community

About me

Recent activity

Subscribe to this feed

  • circa1977 started following the question "What is the % in new dashboard percent of?" in Next Update.

  • problem

    circa1977 replied on April 23, 2009 20:40 to the problem "IE6 Support" in Next Update:

    circa1977
    Thanks, Garrett. I appreciate the response. I can't ask you to invest time in a short-term solution that won't serve long-term needs, or to sacrifice resources on something that offers very, very little return. I know how that situation works all to well, and neither party ends up happy.

    My real lament is that there are no other options out there that I'm comfortable putting in front of clients. Lighthouse seems much less polished and FogBugz brutal on the eyes. Hopefully we can keep time spent on bug tracking to a minimum.

    Mark
    Do you think this solves the problem? Mark it as solved
  • problem

    circa1977 reported a problem in Next Update on April 23, 2009 19:26:

    circa1977
    IE6 Support
    Hi Sifter Team,

    I'm writing about IE6 support.

    Look, I'm a web developer. I understand the efficiencies gained by not worrying about this. Fact is, I have a large corporate client who's stuck on IE6. I've been paying for Sifter so that I could enable an elegant, formal QA process for that client. Then the redesign drops IE6 support.

    Sure there are practicalities and sure IE6's lifespan is limited (my site only gets 5-6% of traffic from it), but the sorts of clients who aren't budging from IE6 are the sorts who can benefit from this service.

    I'm going to have to cancel my account. And that might be fine for you, but it's disappointing to me.

    Mark
  • idea

    circa1977 shared an idea in Next Update on December 09, 2008 17:53:

    circa1977
    Basecamp integration? Issue to To Do migration
    I haven't even entered a ticket yet, but one idea occurs to me: Support access to the Basecamp API and the ability to selectively migrate an issue into a Basecamp To Do. I envision maintaining a separation between project tracking and bug tracking between the two apps, but sometimes the end-user doesn't know what's a big vs. something that should be tackled as part of the project.