When logging a new bug report, it's helpful to the Firefly team when the information in the report includes steps describing how they can reproduce the bug experience. Once we can reproduce an issue, we can start investigating a fix.
Note: If after a bit of troubleshooting, we find that the bug report is, in fact, not a product bug, the bug report may be moved out of Bugs and over to Discussions.
Use the template below as a guide for posting the most meaningful bug reports for the team.
Bug report template:
Issue:
- Device/OS version:
- Browser Version:
Steps to reproduce:
- ...
- ...
- ...
Expected result:
Actual result:
Anatomy of a great bug report:
Issue: Provide a succinct one-line issue statement
(i.e. Firefly does X when...)
Provide Browser version: Google Chrome Version 120.0.6099.71 (Official Build) (arm64)
Provide OS and version: iOS 17/Android 14
Issue: Provide good steps to reproduce the behavior:
Step 1 to reproduce the issue (i.e. Open Text to image)
Step 2 to reproduce the issue (i.e. Click "Upload your image")
Expected result: Firefly should do Y
Actual result: Firefly does X
* Optional, but useful: Upload a Test file (can be shared through CC files or other third-party storage), screenshot, video or gif file capturing the issue
AdChoices