Jira Test Management

Components, affectsVersions, fixVersions can have multiple values, use a comma separated list of their id’s in value field.


jira.png

A default Jira settings form have 8 pre-entered fields-

Project – You have to specify your project key here. Project key is usually mentioned next to project name in bracket and can also be taken from project Index page. It is a required Field.

Type – Here you can specify that the issue type you are reporting is a bug, feature, task etc. Go to add issue page, and click on view source and you will see the value for type in similar format- <option id=”issuetype100002″ style=”background-image: url(/images/icons/newfeature.gif);” value=”2″>New Feature</option>. Value for Bug is 1, new feature is 2, task is 3 and so on. It is a required Field.

reporter – Here you can specify the username of the user who is reporting issues from Test Collab. This field is an optional field, if you will leave this field empty all issues will be set as reported by Project Leader.

assignee – Here you can specify the username of the user to whom you want to assign all issues created from Test Collab. This field is an optional field, if you will leave this field empty all bugs will be assign to default assignee of that project.

priority – You can define the priority of the issue here. Go to add issue page, and click on view source and you will see the value for priority in similar format- <option value=”2″ style=”background-image: url(/images/icons/priority_critical.gif);” class=”imagebacked”>Critical</option>. So, value for critical is 2. Similarly default value for blocker is 1, major is 3, minor 4 & trivial 5.

components – You can define components here. Go to add issue page, and click on view source and you will see the value for components in similar format- <option value=”10000″ title=”Addons “>Addons</option> So, in this case value for our component addon is 10000.

affectsVersions – You can define version in which the issue is manifesting here. Go to add issue page, and click on view source and you will see the value for versions in similar format- <option value=”10000″>1.0</option> So, in this case value for our affected version 1.0 is 10000.

fixVersions – You can define version to which this issue belongs here. Go to add issue page, and click on view source and you will see the value for versions in similar format- <option value=”10000″>1.0</option> So, in this case value for our fix version 1.0 is 10000.

You can click the test button at bottom to make sure that Test Collab is able to create a sample bug in Jira.

Setting up custom Jira Fields

1. Go to Jira’s Enter Bug page.

2. Right click on it and select View source.

3. Find the name and value for Jira’s custom fields. Name for Jira custom starts from customfield_

4. Click on add more field link on Issue Manager Settings page, put your custom field name and value in respective fields.

5. Click Test button to create a sample bug and check if your custom field was added successfully.