Unfuddle Test Management

unfuddle.png

A default Unfuddle settings form have 4 pre-entered fields-

project-id – You have to specify your project id here. Project Id can be taken from project’s URL. For example, if your project’s url is http://gpo.unfuddle.com/a#/projects/18747 then your project id is 18747. This is a required field.

priority – You can define the priority of the ticket here. Go to add ticket page, and click on view source and you will see the value for priorities in similar format- <option value=”5″>Highest</option>, so our value for highest priority is 5. Similarly our value for high is 4, for normal is 3, for low is 2 & for lowest is 1. This is a required field.

assignee-id – Here you can specify the value of the user to whom you want to assign all tickets created from Test Collab. To obtain value of a user, click on view source, and you will see the value for user in similar format- <option value=”11027″>Shriti G.</option>, so our value for user Shriti is 11027. You can similarly find values for other users.

status – You can set the status of your tickets from this field. You have to write full name of priority in your value field of Test Collab, as an example new, reassigned, resolved etc.

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

Setting up custom Unfuddle Fields

1. Go to Unfuddle’s Enter Bug page.

2. Right click on it and select View source.

3. Find the name and value for Unfuddle’s custom fields. Name for Unfuddle custom starts from issue_custom_field_values. For example, we have a custom field name Environment, on viweing page source we see – <label for=”issue_custom_field_values_2″>Environment</label>, so our field name in this case is custom_field_values_2. Now, for value we see in source- <option value=”Development”>Development</option> our value for development environment is Development.

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.