Software Release Process – Ketryx
Why is my item unexpectedly being moved back to Resolved after being approved?
Why is my item unexpectedly being moved back to Resolved after being approved?
Why can't I exclude items that are incorporated from another project through cross-project referencing?
Why does the “Documents approved” field in the release checklist show as completed when my generated documents are not approved?
How does Ketryx update users on new features?
How does Ketryx update users on new features?
What if I attempt to approve an item from the All Items screen, I go through the approval process, and then the item remains unapproved?
Can I archive document templates or store drafts somewhere in Ketryx?
Can I archive document templates or store drafts somewhere in Ketryx?
Can item types or Source IDs be explicitly labeled (e.g., “SYSREQ” for System Requirements, “UNREQ” for User Needs Requirements) instead of the generic “REQ” format?
How can I lock items for a release baseline?
How can I lock items for a release baseline?
Why don't I see an approval button for my release documentation?
Why don't I see an approval button for my release documentation?
What are unchecked items?
I'm using the AI generated summary in my release document template, why am I not getting a response?
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?
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?
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 does Ketryx enable users to work on multiple versions and deployments for the same project?
How can I make document templates require approval?
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 could I effectively use change request items in Ketryx? What are some common practices?
How do I view the approvals and approval history?
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?
I See 1/1 approvals on a ticket. However, Jira still says that I need the owner to sign.
I See 1/1 approvals on a ticket. However, Jira still says that I need the owner to sign.