Ketryx Lifecycle Management

The purpose of this section is to answer questions related to the ongoing usage and operations of the Ketryx Platform, a lifecycle management system built to streamline high-quality software development and support FDA software compliance and compliance with standards such as ISO 13485, IEC 62304, and ISO 14971, among others.

How do I integrate Ketryx with Jira?
Can I defer Anomalies in Ketryx?
Can I approve items in bulk?
What is the difference between a set of incorporated and referenceable items?
Can Ketryx only track parts of a project?
Is it possible to manage branched requirements in Ketryx?
Does Ketryx take into account and record prior ticket history in Jira?
Is the release version in Jira the same as the one in Ketryx?
How can we manage projects in a way that gives devs additional information on how to perform an implementation that will not show up in our regulatory submission?
Is it possible to create a Ketryx project before creating a Jira project?
What options are available for documentation publication?
How is version control ensured for configuration items defined in Jira?
What is a configuration item?
Why am I unable to access or sign off on a ticket in Jira using the approvals widget?
What permissions do organization owners have in comparison to members?
How do I delete a configuration item?
How do I create and organize my Architecture Diagram in Ketryx. Why would I need it?
What are long-lived and point-wise (short-lived) configuration items? What are the differences between the two?
For a software item specification, what is the purpose of the "Input" and "Output" field in Jira?
What is the relation between requirements and specifications? How should I differentiate and manage requirements and specifications?
What is a "use case"?
Do I have to use the provided Ketryx scheme for issue types?