1. Creating custom fields for Clear Plan
For proper work of plugin Clear Plan you need to create several custom fields on the basis of which workplan will be created.
Custom field, which is used as a definition of version where the error was found. This setting is necessary to display the number of errors that were found in version.
Custom field, which is used as display of errors criticality. Error criticalness is fixed to display statistics in the plan by different kinds of errors.
Custom field, which is used as an executor of an issue. This field is necessary in order to work plan can be viewed by each executor separately.
Custom field, which is used as the date of check of an issue. Necessary to calculate the delay of issue execution. If a user sent issue on check, the delay will be calculated between the check date and scheduled execution date. If the issue is not checked, the delay will be considered between the current date and scheduled execution date.
Custom field, which is used as a priority. This field is necessary to be able to specify the order of issue execution to the executor by dragging issues in the work plan.
Custom field with a list of users who can see the issue. Customers who are listed in this issue field, will always have access to issue regardless of the Redmine settings. Using Clear plan you can extend the visibility of issues, automatically copying user into this field from other issue fields.
Custom field that determines copying of issue to the further plans.. It allows you to copy issue from version to version. If you select the appropriate setting, then the issue will be copied to all future versions and will be copied when creating new ones.
Determine the automatic close of version by the field. If this field is selected it allows to close version automatically when all issues in it are closed.
Below is a step by step guide to create each field.
Preferences of created fields may vary depending on your needs. But it is recommended to choose the option For all projects in order to simplify the work.
Select custom field with type Issues, which will be used as the definition of version in which the error was found. Press the button Next.
Create next fields similar to the previous one.
Create custom field with type Issues and format List, which will be used for fixing the errors criticality.
Create custom field with type Issues and format User, which will be used as executor of an issue.
Create custom field with type Issues and format Date, which will be used as check date of an issue.
Create custom field with type Issues and format Integer, which will determine the order of task execution.
Create custom field with type Issues and format User, extending visibility of issues for users recorded in it. Select an option Multiple values for this field.
Create custom field with type Issues and format Boolean, which will define the necessity of copying issue in the following plans.
Create custom field with type Version and format Boolean, which will determine the automatic close of version.