Usage
When a user submits a new bug for a project, there may appear a necessity to enter some extra information. If existing fields for bug submitting do not reflect your company's needs, you may create up to 10 text custom fields or pickup lists that will have to be filled in together with the system-defined fields.
Obligatoriness of custom fields is specified by the project: therefore, after you have created a new field, you should specify in issues of which project it should be present. If you have not marked a field as obligatory for a project, a user submitting a new issue will not be able to see it and fill it in.
Path
Admin tab – Management area – Custom fields link
Procedure
The procedure of custom fields creation comprises two steps:
Step 1. Create a new custom field.
- Press the Edit icon next to an empty line in the Custom fields form.
- On the displayed page, enter necessary values for a created field. If you have selected the Picklist type for a field, enter the list of choices in the displayed window. Every entry should begin with a new line; no punctuation marks are required.
- Press the Submit button to save the new form or the Reset button to discard changes.
Step 2. Specify a project in which a created custom field should be present.
- Press the Project link in the Management area of the Admin section.
- Click the Edit icon next to a project in which the custom field should be present.
- Select Visible next to a newly created custom field.
As a result, created custom fileds will become visible to a user when a new bug for a corresponding project will be created or an existing issue will be edited.
Tips
To specify a default value for a custom field of the Picklist type, select the necessary value from the list when editing a project fields value (on the picture above see the Resolution field example).
Next: Versions