Risk management
Risk management lets you:
- systematically identify potential problems for the project and the product being created (identify risks);
- assess the probability of such problems and the severity of the consequences if they occur;
- define activities and work out technical solutions that reduce either the probability that they occur or the size of the negative consequences.
For more on risk management, see Identifying risks
Project planning
- For an iteration (or a work stage) you can now assign participants and specify their daily availability. This lets you reserve employee time for project stages in advance and find free capacity or conflicts. For details, see Resource planning
- Start and end dates of Tasks and enhancements are calculated from the assignee's schedule. Either the default schedule is used, or the schedule of the team the employee belongs to.
Organizing support
- Response SLA and resolution SLA are calculated from the working schedule. Elapsed time for response or resolution of a Request starts only during the assignee's working hours, or according to the default schedule if the assignee is not yet defined.
- Companies (departments) can now form a hierarchy. The option "Employees see each other's Requests" applies to only one level of the hierarchy. Employees of subsidiary structures in a holding can therefore see Requests only within their own subsidiaries.
Managing project artifacts
- A new application mode was added: "Recycle bin" (enabled in Administration — Settings — Application). In this mode, when main artifacts are deleted, the artifact is not physically removed from the database; it is placed in the recycle bin. You cannot reference such an artifact, but you can easily restore it from the recycle bin. If needed, you can empty the recycle bin, physically deleting the artifact and its links from the database. Open the recycle bin inside the project, in the Management section, or find it through the search window for modules, reports, and artifacts.
- To start an approval you no longer need to choose the "Approve" menu item separately and then move the artifact to the state where approval takes place. It is enough to bind the system action "Create approval" to a transition (for example, To approval). If no template is specified in the system action parameters, the system opens the approval creation form.
Settings
- To require a user to fill a field in a strictly defined format, use regular expressions. A regular expression can be set on the form for a system field or a custom attribute. A regular expression starts with "^", which means the start of the string, and ends with "$", which means the end of the string. Examples of regular expressions:
- ^[А-Яа-яЁё]+$ — a regular expression that checks that only Cyrillic is entered;
- ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$ — a regular expression that checks an email address;
- ^((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)\.?\b){4}$ — a regular expression that checks an IPv4 server address.
- In the administration section you can configure the working schedule and add additional working schedules. A working schedule specifies the working days of the week and the start and end time of the working day. For details, see Work schedule.