Find verification gaps. Use the permitted Jama Connect records and show me the supporting evidence.
Once the API connection is configured, I’ll compare selected requirements with linked test evidence and identify unresolved coverage.
Requirements, related items and test information permitted by your Jama projects and REST API scope.
Find verification gaps
- Findings linked to source records
- Missing evidence and unresolved questions
- Follow-up work for your team
1What’s connected.
Trace requirements to tests and expose missing verification evidence. Scope an API integration so Neil can use the permitted records to prepare analysis, reports and follow-up work.
Connection setup and permissions
Use the Jama Connect REST API. API access requires a Named Creator licence; project permissions still apply.
We scope this connection against the provider’s documented interface for your environment. Start with read access; any source-system changes need separately configured actions and controls.
2Start with the job.
Records in scope: Requirements, related items and test information permitted by your Jama projects and REST API scope. Tell us the job, and we’ll confirm the interface, permissions and implementation scope with your team.
3What Neil can do with Jama Connect once connected
Once the relevant API access and data mappings are configured:
- Find verification gaps
- Compare selected requirements with linked test evidence and identify unresolved coverage.
- Assess a requirement change
- Collect connected items and prepare an impact-review draft.
- Assemble a validation brief
- Summarise the selected scope, evidence and open work with item references.
4Connection questions
Will this work with our Jama Connect environment?
We check your product edition, API availability, authentication and permitted records against the job you want Neil to do. The linked provider documentation describes the interface; Seal does not yet have a guided connector for it.
5Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.