How to report a bug

Jump to bottom

Antonio Robirosa edited this page Apr 4, 2020 · 2 revisions

Goal

To be able to reproduce the issue in my development environment as fast as possible. And that way provide you with a solution as soon as possible

Recommendations

Please create a ticket to report a bug. So you can follow the progress of the issue automatically and I can plan my work load easily.
Fields of the ticket:
- Milestone: Leave this unassigned. This is the version where the bug will be fixed or the feature will be delivered
- Status: Leave it empty. As soon as I read it, I will set it to Accepted.
- Owner: Empty
- Priority:
  - Blocker: This bug is stopping a release in production
  - Normal: Reduction of the functionality of the extension
  - Low: Any other case
- Type:
  - Bug
  - Enhancement: New functionality that you would like to see in the next versions.
  - Task: To comply the non-functional requirements like performance or quality.
- Labels: Add some keywords to help other people find this ticket.
Description of the features: Just include a description of the idea and it benefits.
Description of the bug:
- Details of your environment: Hybris Version, Operating System and Database Engine.
- Version of the Areco Deployment Manager:
- Steps to reproduce the bug:
- Stacktrace: If there is one.
- Code of the deployment script: In some commercial projects, you would have to prepare an sample script.

Thank you in advance! This should be enough to reproduce the bug locally! Now it is my turn to start working!