Software Release Process

The purpose of this section is to answer questions related to the activities that will be performed as part of the release of a product (the Product) managed with Ketryx Lifecycle Management.

What are unchecked items?
I'm using the AI generated summary in my release document template, why am I not getting a response?
How can I see which items need to be approved by a specific group?
Why do my release documents require an update when no changes have been made?
I have versions of my product that I have already released and completed migration into Ketryx. How can I use them as a baseline for my Ketryx project?
How does Ketryx manage product releases that involve cross-project referencing when different versions are utilized in the subsystem projects?
How does Ketryx enable users to work on multiple versions and deployments for the same project?
How can I make document templates require approval?
Does Ketryx have an automated mechanism to send documents from one system to another once they are approved?
How could I effectively use change request items in Ketryx? What are some common practices?
How do I view the approvals and approval history?
What are the Ketryx default release documents and what are the documents omitted by default? How do I re-include them in my release?
We use a different version numbering system from the default Ketryx numbering (major.minor.patch), how can I configure this?