Versions Compared

Old Version 19

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Søren Duusgaard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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.



  2. Click and open the Project-dropdown box and select the relevant project.
  3. Click and open the Issue Type-dropdown box and select the relevant issue type.
  4. Click the Create button.


    This displays Step 2. Enter the details of the issue screen.



  5. Fill in the fields.

    Mandatory fields
    • Summary: An explanatory and recognizable name for the issue.
    • Billable: Indicates whether the issue is billable or not (Change Requests are always billable).
    • 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
    • Priority: Priority of the ticket. 1, 2, 3 or 4 with 1 indicating the highest priority.
    • Severity:Only valid for bugs. Indicates how severe the bug is compared to other bugs of the same priority. This helps indicates the fixing order of bugs (Fatal, Severe or Minor.)
    • 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.

  6. Go to the Release Tab:

    This displays Step 3. Bringing forward the following page:

  7. Fill in the field.

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

...

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
  • P = Project for more than 300 hours