| Label | Description |
|---|---|
 |
Bug report contains sufficient information to reproduce. Will be solved for associated Milestone. |
 |
Improvement accepted. Will be added for associated Milestone. |
 |
Issue has been solved and will be applied in the associated Milestone. |
 |
Issue has been already reported and will be closed with no further action. |
 |
Issue has not been created according to requirements at the Issue reporting guidelines. Will be closed until requirements are met. |
 |
Feature request to be considered by the team. After approval will be labeled as enhancement. |
 |
The team was not able to replicate issue. It will be closed until missing information is given. |
 |
Contact our support team at [email protected]. Issue will be closed with no further action. |
 |
Issue is considered as low priority by the team. |
 |
Issue is considered as high priority by the team. |
 |
Issue reports a conflict with other third party extension. |
 |
Feedback is required to continue working on the issue. If there is no answer after a week it will be closed. |
 |
Issue can not be solved due to external causes. |
 |
Issue will be closed. Available documentation: MailChimp For Magento doc |
To maintain an effective bugfix workflow and make sure issues will be solved in a timely manner we kindly ask reporters to follow some simple guidelines.
Before creating an issue, please do the following:
- Check the documentation to make sure the behavior you are reporting is really a bug, not a feature.
- Check the existing issues to make sure you are not duplicating somebody’s work.
- Make sure, that information you are about to report is a technical issue, please refer to the Community Forums for technical questions.
If you are sure that the problem you are experiencing is caused by a bug, file a new issue in a Github issue tracker following the recommendations below.
Title is a vital part of bug report for developer and triager to quickly identify a unique issue. A well written title should contain a clear, brief explanation of the issue, making emphasis on the most important points.
Good example would be:
Unable to place order with Virtual product and PayPal.
Unclear example:
Can't checkout.
Describing preconditions is a great start, provide information on system configuration settings you have changed, detailed information on entities created (Products, Customers, etc), Magento and mc-magento versions. Basically, everything that would help developer set up the same environment as you have.
Example:
1. Magento CE 2.0.1 without sample data is installed.
2. mc-magento 1.0.6.
3. Test category is set up.
4. Virtual Product is created and assigned to the Test Category.
...
This part of the bug report is the most important, as developer will use this information to reproduce the issue. Problem is more likely to be fixed if it can be reproduced.
Precisely describe each step you have taken to reproduce the issue. Try to include as much information as possible, sometimes even minor differences can be crucial.
Example:
1. Navigate to storefront as a guest.
2. Open Test Category.
3. Click "Add to Cart" on the Virtual Product.
4. Open mini shopping cart and click "Proceed to Checkout".
...
To make sure that everybody involved in the fix are on the same page, precisely describe the result you expected to get and the result you actually observed after performing the steps.
Example:
Expected result:
Order is placed successfully, customer is redirected to the success page.
Actual result:
"Place order" button is not visible, order cannot be placed.
Additional information is often requested when the bug report is processed, you can save time by providing Magento and browser logs, screenshots, any other artifacts related to the issue at your own judgement.
Before creating a pull request please make sure to follow this guidelines or it will be rejected.