Skip to main content
Version: 1.5.2

Version 1.5.1

In the new version we have added system events and configured notifications based on them. Through this, the users can receive updates about important changes in their tasks and releases. We have also created system properties for the administrator to define global settings of the notifications sent from the SDLC application.

Another important feature is the ability to add task dependencies. Now, the users can register the relations between tasks and the nature of these relations in the system, defining their type and direction (which task is the initial and which is the dependent one). By default, four dependency types are available, but the administrator can add more options to precisely reflect the business processes of their company in the system.

We have also made improvements and fixes to project boards and product modules.

New features​

Events and notifications​

We have created the rules that add records to the Event (sys_event) table when certain conditions are met in the SDLC application. When this happens, the users automatically receive email notifications. The list of the configured notifications:

  • A task is added to the project – the notification is sent when the Project of the task changes.
  • A task has been updated – the notification is sent when the value of one of the following task fields changes: Name, Description, Acceptance criteria, State, Assigned user, and also when a work note or a comment is added to the Discussion of the Activity Feed.
  • A release has been updated – the notification is sent when the value of the release State changes, and also when a work note is added to the Activity Feed.

Each notification has a limited circle of recipients. Though we have provided the translations here, in the Release Notes, in the system the notifications are currently only available in Russian. You can modify them accoring to your language and preferences.

Detailed information about the new events and notifications is available in the documentation.

Additionally, we have added the system properties that the administrator can use to define global configuration of the SDLC noticaitions:

  • sdlc.notification.logo_href – the image URL for the logo displayed in the SDLC notifications.
  • sdlc.notification.instance_href – the URL to the instance referred to in the SDLC notifications.
  • sdlc.notification.instance_title – the instance title to be displayed in the SDLC notifications.

Read more about the new system properties in the documentation.

Task dependencies​

We have developed a functionality that allows users to register the relations between the tasks in the system. To implement this, we have created the following tables:

  • SDLC Task Dependency (pda_task_dependency) – an M2M table that contains records of relations between tasks, defining their type and direction (which task is the initial and which is the dependent one).
  • SDLC Task Dependency Type (pda_dependency_type) – a table that contains types of possible dependencies between tasks. By default, four standard options are available, but it is possible to add other options that will precisely reflect the business processes of your company.

To create a task dependency, use new Add dependency UI action located on the forms of SDLC tasks of all types. Clicking the button opens the Add task dependency modal window where you can specify the dependency details.

You can also create a dependency from the Task Dependencies related list added to the forms of tasks of all types. The list contains all dependencies in which the task is specified as the initial or dependent one.

Similar related list has been added to the Project form. It contains all dependecies of the tasks related to the project.

Read more about the dependencies in the documentation.

Improvements​

Update of access rights to the task board UI actions​

Now the Add tasks to backlog, Create task, Start sprint, Complete sprint, Sprint planning UI actions of the task boards are available to all the project team members and not only to the project team leader and the owners of the product/product module specified in the project as it used to be in the previous SDLC versions.

Fixes​

DEF0018880: The WIP limit and Board area columns that are relevant only for Kanban boards could be edited on the Scrum board form in the Columns related list. Now these columns are read-only for Scrum boards.

DEF0018840: A product owner was unable to create child modules for their product. The issue has been fixed, and now such a module is saved correctly. We have also extended the access rights for editing the product modules: currently, the operation is additionally available to the users with the pda_user role who created the module record or are the owners of any other module of the same product.