Ticket/Issue API or Embed ability

The API is already in the works. As for issue submission, that's a little more complex. Within Sifter, accountability is one of the two most important facets of an issue. Without being logged in, we have no way of knowing who submitted the issue.

In terms of remembering login information, we do offer OpenID, and that makes it incredibly easy for people to login without having to remember a password.

There are several factors at play here. Sifter is a bug and issue tracker designed for a discrete number of internal team members. It's not yet designed to work as a public-facing help desk for an indeterminate audience. Offering a public submission form is more of a help desk thing. While there is some overlap in functionality, bug trackers and help desks are two very different beasts. (I wrote a "post talking in depth about the distinction":http://nextupdate.com/blog/archives/2009/03/help-desks-vs-bug-trackers/.)

That said, we do have plans to add an integrated help desk option. It would support the scenarios that you're talking about, but at this point, it's still in the design phase. Once we open up the application to those scenarios, we'll inevitably need to fight spam, so that will be a new challenge for us since Sifter is currently locked down to authenticated users only.

We're not sure exactly how or when the help desk plans will unfold, but it's something we want because we need it to help us support Sifter.