A useful bug report tells the next person what you did, what you expected, and what happened instead. You do not need to know why the app failed to report it clearly.
You need access to the project and permission to create an item. Your organization may use a custom form, so the required fields can differ.
File the report
- Select Create, which is labeled Create new item for screen readers.
- In the create form, choose Bug for something that went wrong. The standard form is titled New Bug; your organization may use a different form name.
- Open Optional project details and choose the relevant Project when the form offers it.
- Enter a specific title. For example, "Save does not close the settings form" is more useful than "It is broken."
- In Description, explain what you were trying to do. If your configured form uses different fields, put the relevant details in the fields it provides.
- In Steps to Reproduce, list the steps in order so someone else can try them.
- In Expected Behavior, describe what should have happened. In Actual Behavior, describe what happened instead.
- Complete any other required fields and select Create Bug, or the matching Create button for your organization's form.
- Open the saved item and check that the report contains what you intended.
If Potential Duplicates Found appears, read the suggested reports before creating another one. If the same issue already exists, a comment with your additional details may be more useful.
Connect the report to a feature
If you found the problem while testing a specific feature, open that feature and select Report Bug. You can also use Reported against feature in the normal bug form. Leave it blank when the problem is not tied to a particular feature.
A feature request describes something you want added. A bug describes something that is going wrong. Choose the type that best fits the report.