Draft an idea or a private bug report

Step 1

Draft an idea or a private bug report

1. Open Roadmap & Ideas > Submit
2. Start with one constructive topic

Open Roadmap and Ideas, then Submit. Use this form for one constructive feature idea or bug report.

Step 2

Choose Feature for a suggestion

1. Select Feature
2. Describe the improvement you want

Choose Feature for an improvement or new capability. Explain the problem it would solve rather than listing unrelated requests.

A feature submission is reviewed before public display. Choosing Feature does not guarantee that the request will be planned.

Step 3

Choose Bug for a reproducible issue

1. Select Bug
2. Explain steps, expected result and actual result

Choose Bug for something that is not working. Describe clear reproduction steps, what you expected, and what happened.

Bug reports start private to you and the development team. A sanitized summary may later be published; do not include sensitive details.

Step 4

Write a useful title and description

1. Title: 5 to 100 characters
2. Description: 20 to 2,000 characters

Write a title between five and one hundred characters, and a description between twenty and two thousand.

Keep account numbers, transactions, passwords, logs and device identifiers out of the text. No file or diagnostic attachment is added automatically.

Step 5

Valid text still needs deliberate agreement

1. Read the guidelines
2. Agree only after understanding them

Valid text alone is not enough. Submit stays unavailable until you agree to the community guidelines.

That agreement is for this community submission. It does not enable cloud expense AI or upload your ledger.

Step 6

Read the community and privacy details

1. Use the information control beside the agreement
2. Read moderation, identity and privacy

The information control opens Community guidelines and privacy. Read how feature ideas, private bug reports and installation identity are handled.

This reusable dialog mentions optional account linking, but Pennie's host remains guest-only and offers no account-link or sign-in controls here.

Step 7

Keep a draft without submitting it

1. Expand Draft & similar ideas
2. Use Save draft for an explicit local save

The form autosaves its draft on this device. Expand Draft and similar ideas to use Save draft explicitly.

Saving a draft is not a server submission or a cloud backup. Keep the same installation and storage if you want to retain access.

Step 8

Returning reloads the same draft

1. Leave the page and return
2. Review the restored text before submitting

When you leave this page and return, the actual form reloads the saved draft. Our example retains the same draft and request identity.

Switching tabs alone keeps the existing form in memory; it is not evidence that a draft was reloaded from storage.

Step 9

Check public ideas before submitting

1. Use Check for similar ideas
2. Read the matching public suggestions

Check for similar ideas searches the community board using your title text. It does not use an offline guess or cloud expense AI.

The first Submit also performs this check. Read the result, then choose Submit again only if you still want to send this request.

Step 10

An idea is received before it is public

1. Read the receipt status
2. Pending moderation is not public posting

After confirmation, the page says your idea was received and is awaiting moderation before public display.

The editable form and local draft are cleared only after confirmation. This example is received by a synthetic service, not the live community.

Step 11

Read the private bug receipt separately

1. Check the private bug acknowledgement
2. Do not mistake it for a public idea

A confirmed bug report receives a distinct private-report acknowledgement for the development team.

Keep its description constructive and free of sensitive information. Private visibility does not make unnecessary personal data safe to submit.

Step 12

Unconfirmed delivery keeps the exact draft

1. Do not create a fresh duplicate request
2. Read Retry unchanged submission

If the response is lost, the service may already have received your request. The form keeps the exact draft and freezes editing.

Use Retry unchanged submission to check that same request. Do not repeatedly create a new idea because confirmation was delayed.

Step 13

Safe replay confirms one submission

1. Retry the preserved request
2. Check the receipt and cleared draft

Our lost-response example retries the same request and confirms exactly one stored idea, not two.

Once confirmed, review its receipt and find it later in My activity. Draft save, server receipt and public moderation remain separate stages.

Step 14

Choose, explain, review, then submit

1. Pick the right type and write safe details
2. Review similar ideas before sending

Choose the right type, write clear safe details, read the guidelines and review similar public ideas.

Save locally if you are not ready. Submit deliberately, and use the unchanged retry path if delivery is uncertain.