Create a 'New Issue'

Create 'New issue'

Issues are added under projects and there are three different Issue types in CDrator Jira:

Bug
Any bug in a delivery, a correction of a bug in a configuration, or a bug in the core standard release.

Change Request
Any new change introduced to the existing customer setup.

Customer Request
Any enquiry relevant to the customer specific setup or to the standard Rator system.

To create a new issue:

Click the Create Issue link in the top right side of the browser (on every page) to create a new CDRator JIRA issue.

This displays the Step 1. Choose the project and issue type screen below.
Click and open the Project-dropdown box and select the relevant project.
Click and open the Issue Type-dropdown box and select the relevant issue type.
Click the Create button.

This displays Step 2. Enter the details of the issue screen.
Fill in the fields.

Mandatory fields
- Summary: An explanatory and recognizable name for the issue.
- Billable: Indicates whether the issue is billable or not (not relevant for a Change Request).
- Environment: Indicates in which environment the bug exists (only for bugs).
- Description: It is important to fill out a thorough and complete description of the issue.
  
  Optional fields
- External ref.: If the customer needs to identify the issue in their own system.
- Security Level: Can be set to either Internal or None
- Server: If name of server is available (only for bugs and bugs (non-production)).
- Reproducing: Description of steps and frequency (only for bugs).
- Component/s: In what area is the change needed og bug found. Select from the drop-down list.
- Labels: More detailled information on the area of focus. Select from the drop-down list.
Go to the Release Tab:

This displays Step 3. Bringing forward the following page:
Fill in the field.

Mandatory Field:
- Affects Version/s: Choose the version (release) the CR or bug is affecting.

Priority of Issue

Issue type/priority	1	2	3	4
Bug in production	Problem where the entire or a critical part of the system is unusable, causing major (financial) business impact for the customer	Non-critical problem with a significant business impact and significant restrictions of the use of the system	Problem causing minor impact and with no requirement for an immediate fix, but which should be fixed within reasonable time	Any issue without impact on business, but which would nevertheless be beneficial to the end users.
Bug in non-production	Bug is preventing the work of QA or receipt of the delivery	The bug is preventing things to get in production	The bug is serious, and should be fixed, but it is without major impact in production	We are aware about the bug and decided to move ahead without fixing it for now
Change request	Requests will be included in a planned future release according to priority	Requests will be included in a planned future release according to priority	Requests will be included in a planned future release according to priority	Requests will be included in a planned future release according to priority
Question	Reasonable amount of time	Reasonable amount of time	Reasonable amount of time	Reasonable amount of time

Definition of T-Shirt Estimates

For internal planning purposes CDRator use the below codes:

The T-shirt estimate covers time for all involved departments, i.e. BC, AC, Product and QA (if QA is requested).

XS = 1 - 7 hours will be set to 7 hours
S = 8 - 12 hours will be set to 12 hours
M = 13 - 50 hours will be set to 30 hours
L = 51 - 120 hours will be set to 85 hours
XL = 121 - 300 hours will be set to 210 hours