Dinosaurs did not adapt to the environment and hence they perished. Cockroaches did that trick well and still living. Same for any tool.
Recently we received a set of questions from customers - but most of those questions followed the same tone - "How can I make the tool to adapt to my project?". I am used to some names and the tool does not have those, what to do?
The UI must show the exact labels that the users are familiar with. Else, they may feel that the tool is not capturing the data they want to.
Here is the simple 10 minutes exercise you need to do.
- What fields you want to capture in requirements, test case, tasks and defects? First list them out.
- Login as eadmin to your enterprise, Go to settings, go to System Defined Fields.
- Check whether the list of fields you have is there in the respective module such as defects.
- For example, you need a field called "Importance" and there is a field called "Priority".
- In that screen, change the label of the field Priority to Importance.
- This way, there may be fields already available, but you call it by one name and the tool calls it by another name; just rename in the tool.
- Log out and relogin; go to the project that you configured. Click on new defect. You will see the same field names that you wanted. This is half the battle won.
- Mark those fields that you have in list that are not in the tool.
- For example, you want a field called Browser as a list box, with values MS IE, FireFox, Chrome.
- Login as eadmin to your enterprise, Go to settings, go to User Defined Fields.
- In the defects module, add a new field, with field label as Browser and type as single selection list box and add these values as comma separated ones.
- Repeat the above step for all the fields that are not in the tool.
- Log out, relogin and go to the project. Create a new defect.
- Now you will see those new fields that you want, right in front of you.
This way, you can make the tool to adapt to your templates.