Project Settings

Project settings in Ketryx

Project settings in Ketryx are used to configure various aspects of a project, such as design verification, test management, release controls, and more. These settings are used to customize the behavior of Ketryx for a specific project, particularly to opt in or opt out of various computational controls enforced by Ketryx.

Design verification

Design verification settings are used to configure the design verification process for a project.

Require controlled design inputs before a design output can be approved

If this is activated, an item can only be approved once all its design inputs are in a controlled state.

Require re-verification of affected items after change control

If this is activated, after an item is changed and enters a controlled state again, Ketryx will automatically unclose any other items affected by the change, i.e. transition any design outputs of the changed design input that are currently Closed back to Resolved, so they will need re-verification before entering a controlled state again themselves.

You can see all affected items using a filter on the items screen called Re-verify affected items.

Create re-verification flags for affected design outputs when design inputs change

When enabled, Ketryx will automatically create re-verification flags for design output items that may be affected when a design input item completes change control (re-transitions to a controlled state after being modified). More information can be found here.

These flags serve as reminders to review and verify that the design output items are still valid and up-to-date, given the changes to their related design inputs.

Flags can be dismissed explicitly by clicking "Dismiss" or can be dismissed implicitly by the flagged item completing change control (re-transitioning to a controlled state after being modified).

You are able to filter for flagged items using the KQL filter (which can be used in settings like the Invalid items filters or Custom KQL filters):

is:flagged

Test management

The test management settings are used to configure the test management process for a project to customize the behavior of Ketryx for a specific project.

Require a manual test execution for each effective automated test execution

If enabled, a manual Test Execution item has to be created for the latest automated test execution, before the test is considered passing.

This provides a way to enforce that each automated test is reviewed and electronically signed by itself, in addition to signing the overall testing report.

This applies to automated test executions associated with a Test Case, not to automated tests that are directly associated with a Software Item Spec or other item.

Require automated tests to be associated with test cases

If enabled, automated tests reported to Ketryx are only considered if they are directly associated with a Test Case item. Automated tests associated with Software Item Specs or other items are not considered part of the test plan and testing report.

Allow controlled failed test executions

If this is activated, failing test executions do not block a release, as long as they are in a controlled state.

Inherit excluded tests

If this is activated, Test Executions from the previous release will be considered effective for Test Cases that have been excluded from a version's release test plan.

Require test executions after controlled test cases

If enabled, a Test Execution will only be taken into account if it was created after the Test Case entered a controlled state.

Automatically update release test plan based on external test plan(s)

If enabled and there are external test plans items defined for a version, the overall Ketryx release test plan for the version will be updated automatically to include the tests from those external test plans items.

Release controls

The release control settings are used to configure the release control process for a project to customize the behavior of Ketryx for a specific project. This enables you to enforce certain controls on the release process, or disable them if they are not needed.

Require controlled dependencies

If this is activated, a release can only be approved if all dependencies are in a controlled state.

Require controlled items

If this is activated, a release can only be approved if all items are in a controlled state.

Require a controlled test plan

If this is activated, a release can only be approved if the test plan is in a controlled state.

Require generated release documents

If this is activated, a release can only be approved if all required release documents are generated.

Require uploaded build documents

If this is activated, a release can only be approved if all required build documents are uploaded.

Require up-to-date release documents

If this is activated, a release can only be approved if all required release documents are up-to-date.

Require approved release documents

If this is activated, a release can only be approved if all required release documents are approved.

Require full traceability

If this is activated, a release can only be approved if all items are fully traceable. See the Traceability Configuration reference and MAN-07 Traceability for more information.

Require controlled milestones

If this is activated, a release can only be approved if all milestones are in a controlled state.

Training

Require training

If this is activated, users will be required to complete training before they can approve items. For example, if a group has assigned training, Members must perform that training, or they will not be able to perform actions (i.e., approvals) as part of the Group.

Risk management

The risk management settings are used to configure the risk management process for a project to customize the behavior of Ketryx for a specific project.

For even more fine-grained control over risk management using the advanced settings, please see MAN-08 Risk Management.

Require harm and initial severity selection

If enabled, users are not able to set a custom harm or initial severity value. Instead, they may only select a pre-defined harm, and the associated initial severity of that harm is enforced.

Require derived risk analysis fields

If enabled, users are not able to modify the derived risk analysis fields (i.e. initial and residual risk evaluation, risk acceptability).

Require hazard selection

If enabled, users are not able to set a custom hazard. Instead, they may only select a pre-defined hazard.

Require hazardous situation selection

If enabled, users are not able to set a custom hazardous situation. Instead, they may only select a pre-defined hazardous situation.

Deleting a project

If a user wants to delete a project in Ketryx, click the 'Delete project' button at the bottom of the project settings. Doing this will require the user to type the name of the project they are currently attempting to delete and provide their security key. After checking the 'I confirm I want to delete this project' box, the user will be able to delete the Ketryx project. Once a Ketryx project is deleted, there is no way to recover it.