|
1 | 1 | --- |
2 | | -description: You can report encountered issues to Ibexa DXP JIRA or use it to follow the development of new features and fixes. |
| 2 | +description: You can report encountered issues to Service Portal |
3 | 3 | --- |
4 | 4 |
|
5 | 5 | # Report and follow issues |
6 | 6 |
|
7 | | -[[= product_name =]] uses [JIRA](https://issues.ibexa.co) to track product development, improvements, and bugs. |
8 | | - |
9 | | -## Finding an existing issue |
10 | | - |
11 | | -Before you create a new bug report or an improvement suggestion, |
12 | | -search the JIRA project for similar reported issues. |
13 | | -If you find any, update them with your comment or additional information instead of creating a new one. |
| 7 | +If you have an [[= product_name =]] subscription, report your issues through the [Service portal](https://support.ibexa.co). |
| 8 | +To do it, log in to your Service portal at <https://support.ibexa.co/>, click "New Ticket", and report the issue as you would report a normal support request. |
| 9 | +[[= product_name_base =]] Product Support will respond, take care of the report, and keep you informed of the developments. |
| 10 | +This ensures the issue can be quickly prioritized according to its impact. |
14 | 11 |
|
15 | | -## Reporting an issue |
| 12 | +## Reporting security issues |
16 | 13 |
|
17 | 14 | !!! caution "Security issues" |
18 | 15 |
|
19 | 16 | If you discover a security issue, please do not report it using regular channels, but instead take a look at [Security section](../guide/reporting_issues.md). |
20 | 17 |
|
21 | | -If you have an [[= product_name =]] subscription, report your issues through the [support portal](https://support.ibexa.co) instead of JIRA. |
22 | | -This ensures the issue can be quickly prioritized according to its impact. |
23 | | - |
24 | | -If you cannot find an existing ticket matching what your issue, you can create a new one. |
25 | | -Click **Create** at the top of the bugtracker window and fill in the following fields: |
26 | | - |
27 | | -||| |
28 | | -|------|------| |
29 | | -|**Project**|Select **Ibexa IBX**.| |
30 | | -|**Issue type**|Choose **Bug** or **Improvement** depending on what you are reporting, do not use other issue types (they are for internal use only).| |
31 | | -|**Summary**|Write a short sentence describing what you are reporting.| |
32 | | -|**Priority**|Select the priority you consider the issue to be. Please try to keep a cool head while selecting it. A 1 pixel alignment bug is not a "blocker".| |
33 | | -|**Component/s**|This is important, as it will make your issue appear on the radar (dashboards, filters) of people dealing with various parts of [[= product_name_base =]] projects.| |
34 | | -|**Affect version/s**|Add the versions of the application you experienced the issue on.| |
35 | | -|**Assignee**|Leave blank, unless you are willing to work on the issue yourself.| |
36 | | -|**Reporter**|Leave as is (yourself).| |
37 | | -|**Environment**|Enter specific information regarding your environment that could be relevant in the context of the issues.| |
38 | | -|**Description**|This is the most important part of the issue report. In case of a bug, it **must** contain explicit steps to reproduce your issue. Anybody should be able to reproduce it at first try. In case of an improvement, it needs to contain use cases and detailed information regarding the expected behavior.| |
39 | | -|**Product**|Select which flavor of [[= product_name =]] the issue concerns.| |
0 commit comments