Skip to main content
Version: 1.8.1

Patch 1.8.1

In the new SDLC version, we have added dynamic identification of the initial state relevant for the selected task type, and a validation to ensure the state option selected by the user is included in the state model that will be applied to the task after its creation. Moreover, now you can specify a product different from the one specified in the project on the forms of tasks related to projects dedicated to product development. We have also fixed several errors in the application logic.

Improvements​

Setting an initial state appropriate to a task type​

We have improved the states logic, so now when you add a task from the SDLC Task (pda_backlog_item) form, its child table's form, or from the related list on the Product form, the default state value is the state option with the lowest Order among the states available for the selected task type. This change addresses the differences between the states configured for task types.

Now, when you add a task using the methods mentioned above, you can select any state available for the task type, and the system will check if this state is included in the state model that will be applied to the task type after the creation:

  • If the Project is specified and there is a suitable State Models in Project record, the system verifies if this model includes the selected state. If there is no state model in project record, the verification is not performed.
  • If the Project is not specified, the system verifies if the selected state is included in the state model specified on the task type form.

If the selected state is not included in the applied state model, you will see a warning message on the form asking you to change the value and avoid limitations when working on the task.

Read more in the documentation.

The reference qualifier of the Product field on the SDLC tasks' forms is not fixed anymore, so you can now specify a product different from the one specified in the related project, or a product in the Archive state. Additionally, the Project field is no longer cleared when you change or clear the product.

Fixes​

DEF0020276: The Product field was not completed automatically when a product module was created from the project form, making it possible to specify unrelated product and module on the project form. From this version, the Product field is completed automatically and read-only in this case.

DEF0018266: The Sprints related list was not displayed on the forms of the projects where the Product development checkbox was not seleted. Now, the sprint list is displayed irrespective of the checkbox's value.