API does not allow posting anonymous issues

Issue #7752 wontfix
Riot created an issue

The API allows posting issues but only if authenticated with a valid account if the repository is a private one, even when the issue tracker is public:

It doesn't make sense to have a feature missing from the API that is available through the ordinary browser. It would be very useful to allow anonymous issue posting this way, since it would enable the development of apps that have an internal bug reporting feature.

(however, anonymous issue posting in browser also appears broken at the time of writing - see issue #7751)

Comments (6)

  1. Jesper Noehr

    We've closed this off, as it was a vector for spam. I don't see a good way to reopen this API for the time being.

  2. Riot reporter

    Just to clarify - does that mean that it's no longer possible to post issues anonymously at all?

  3. Former user Account Deleted

    Make it optional at the Issue Tracking settings, let us choose if spam is a real problem

  4. Peter van Gulik

    Anonymous issue creation currently is a broken feature in my honest opinion. I want to integrate the creation of issue in my application and allow users to easily create an issue and include already some diagnostic logs automatically. Also I want to know who raised the issue, having a way to contact the raiser of the issue.

    My suggestion would be to create a new API (or update the existing one) specifically for creating issue without having an active account on bit bucket. The API would require you to specify your mail address on which you will also receive notifications in case the issue is updated. In case the e-mail used to create the issue has an active bit bucket account associated to it you cannot use it to create an issue and instead should authenticate (API returns an 401 error in that case). As it already is an option to disable anonymous issue creation.

  5. Marco Franke

    It would be great if you set your issue tracker to public, the API and web will behave identically.

  6. Log in to comment