Good practices: management of the issues library

In order to guarantee optimal use of our application we recommend these good practices in order to save time.

/!\ Do not confuse issue type with commentary /!\

An issue type is a general, clear and concise description which is reusable for several issues. It thus allows you to find and add multiple issues more quickly.

Also, we recommend that you use a subject then an action verb, nothing more. Example: Radiator to change

A commentary is a detailed description, particular to an issue which can be supplemented by a photo, depending on the detail desired.

Example: Several scratches visible on the right-hand side

This is even more important, when you have several tablets on the same construction site or even newly arrived users who are untrained in the use of FINALCAD.

Here are the mistakes to avoid:

/!\ If you have not pre-filled in the list of issue types /!\ 

Each of the users will create their trades and/or their issue types, with their spelling or their syntax. As a result, after synchronisation, several reports are generated for the same trade.

For the same reason, you cannot determine the most frequent defaults due to different names (complex project completion analysis).

Example Trade/Company:

• Exterior Carpentry Co
• Exterior Carpentry
• Ext. Carpentry Co
• Ext. Carpentry
• Exterior Carpentry Co
• Trade 1 - Exterior Carpentry

Issue types example:

• Radiator to be changed several scratches visible on the right-hand side
• Radiator with visible scratches on the right-hand side
• Radiator to be changed because of several scratches

Consequences of poor utilization:

• Assigning an issue will be more complicated because you will not know which trade/issue type to use
• The "Filter" tool will be unusable (we cannot filter several trades)

We strongly recommend the following practices:

• Fill out a list of issue types in advance
• Limit the library editing rights to certain users (manager.finalcad.com "Library editor")
• Offer "Other" as an issue type in each trade, which could be used when the user cannot find a suitable type. A user authorized to edit the library may update the library (add a new issue type or reallocate one of them).