Skip to content

Filing a ticket

Select New ticket in the top bar to report something broken, or ask for something new. You need to be signed in: signed out, the page says Sign in to file a ticket and takes you back to the form once you have.

The form is numbered from 01 to 05, top to bottom.

Choose the app the ticket is about. Each tile shows the app’s name and its one-line description. Only apps that are taking new tickets are offered here; an app that isn’t still has its list, where you can vote on and comment on its tickets.

Choose what kind of ticket it is:

  • Something’s broken: it doesn’t do what it should, or it used to work and doesn’t now. This files a bug.
  • An idea: something it doesn’t do yet. This files a feature request.

The questions further down change to match.

One line: what’s wrong, or what you’d like. Up to 120 characters. The title is what people see in the list, so make it say what the ticket is about.

As you type the title, Forge looks for tickets that might be the same thing and shows up to three under it, headed Is it one of these? The chosen app’s tickets come first. Each shows its title, number, app and status, with its vote box.

If one of them is what you were going to report, vote on it instead: a vote on an existing ticket counts for more than a second ticket. You can vote right there on the form, or open the ticket to read it first. If none of them is it, carry on and file yours.

Tickets that have been closed as duplicates, and tickets in archived apps, are never suggested.

If your browser isn’t running Forge’s scripts, the suggestions appear after you select File ticket instead. The form comes back with Is it one of these? above your details and a File it anyway button. Any screenshots you’d chosen need choosing again.

The questions depend on what you chose under Bug or idea?

For a bug:

  • What happened? This one has to be filled in.
  • What did you expect?
  • Steps to reproduce (optional). One step per line; they’re shown as a numbered list.
  • Browser and device: filled in from your browser, such as Firefox 143 on macOS. Change it if the problem is on another device.

For an idea:

  • What would you like? This one has to be filled in.
  • What would it help you do? The problem behind the idea helps most. There may be a simpler way to solve it.

Each answer can be up to 5,000 characters, as plain text. Leave a blank line between paragraphs. Anything longer is refused rather than cut short, so you can decide what to leave out.

Screenshots are optional. Drop pictures on the box, or select choose files. The chosen files are listed by name and size.

  • You can add up to 4 screenshots, each up to 5 MB, unless the maintainer has changed those limits. The form shows the current ones.
  • PNG, JPEG, GIF, WebP and AVIF work. Anything else is refused.
  • iPhone photos are often HEIC, which most browsers can’t show, so Forge refuses them and says how to send a JPEG instead: on an iPhone, share the photo to Files and pick Save as JPEG, or set Settings › Camera › Formats to Most Compatible. A screenshot saves as PNG, so it’s fine as it is.
  • If you choose more than the limit, the first ones are kept and the rest are left out.
  • Your screenshots, on tickets and comments together, can take up to 100 MB. Your data in Settings shows how much you’ve used.

Before a picture is stored, Forge takes out the hidden details a camera or phone adds to it, such as where it was taken, so a photo never gives away where you were.

Big pictures are shrunk in your browser before they’re sent: anything over 2,400 pixels on its longest side is scaled down, and anything over the size limit is made smaller to fit. A PNG that is still too big is sent as a JPEG. GIFs are sent as they are, so an animation keeps every frame.

You can’t add screenshots to the write-up later, even when you edit it. To show something new, add it to a comment instead. See Adding screenshots to a comment.

Select File ticket. If something’s missing, the form comes back with a list of the problems at the top and each one beside its field, for example Say what happened., with everything you’d typed still in place.

Once it’s filed, you’re taken to your new ticket, which says Filed. Thanks for taking the time. You follow it automatically, so you hear when it changes. See Following a ticket.

You can change the title and write-up of a ticket you filed at any time, unless its app has been archived. The maintainer can edit any ticket’s write-up too.

  1. On the ticket, select Edit.
  2. The write-up turns into the form’s fields where it stands. Change what you need to.
  3. Select Save changes, or Cancel to leave it as it was.

Saving shows in the timeline as an edit, edited the write-up or edited the title and the write-up, so everyone can see the ticket changed. Nobody is emailed about an edit.

You can’t change a ticket’s app or type yourself. If you filed it against the wrong app, or as a bug when it’s an idea, say so in a comment and the maintainer can move it.