Hey Folks!
When logging a new bug report, it's helpful to the Community Product team when the information in the report includes steps describing how they can reproduce the bug experience. Once we can reproduce an issue, then we can start to investigate 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
Browser & Device type:
Issue:
Steps to reproduce:
- ...
- ...
- ...
Expected result:
Actual result:
Anatomy of a great bug report (example from Photoshop Community):
Issue: Provide a succinct one-line issue statement
(i.e. Photoshop does X when using a tool or plugin)
Provide Photoshop version: Help>System Info>Copy the top line with Photoshop version
Provide OS and version: macOS 12.2
Issue: Provide good steps to reproduce the behavior:
Step 1 to reproduce the issue (i.e. open a new CMYK document)
Step 2 to reproduce the issue (i.e. add layer or use tool)
Step 3 to reproduce the issue (i.e another needed step)
Expected result: Photoshop should do Y
Actual result: Photoshop 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
Cheers,
David
Community Product Manager