Where do your Jira stories meet your SysML model? In many teams, in a spreadsheet that somebody updates by hand before every review.
We introduce yet another great use case and connection using our out of the box stand alone integration tool Reqtify. It has 100+ connectors, ability to create new, and even custom companions as we demonstrate here today!
Scenario is as following Jira work items traced to the SysML model, without copying anything between tools. Reqtify reads the committed model from Teamwork Cloud and keeps the two in step.
Three use cases:
▪ Plan the work find every requirement without a Jira story
▪ Assess a change across model and work items
▪ Audit the release: a GitLab job runs the coverage check on each commit and opens Jira tasks for what it finds!!!
Video
https://www.youtube.com/watch?v=gRfqZQoZOVY
Use Cases
1. Plan the work against the model. The systems engineer commits the model, the product owner plans stories. Reqtify lists every software requirement that has no story yet. The missing stories are created before the sprint starts.
2. Assess a change request. A change request in Jira names the requirement it touches. Reqtify's impact analysis returns the affected requirements, blocks, test cases and open work items. That list is the regression scope, and it goes on the request as a comment.
3. Audit the release. A commit on the release branch starts a GitLab job that runs Reqtify in batch mode. Uncovered requirements, references to unknown IDs and work items without a Covers line become Jira tasks. The job fails while findings remain, so the pipeline is the release gate. Once fixed, the report is the evidence.
The red connectors in the views are the custom parts: the Covers rule in the Jira type, and for the audit the GitLab job with its trigger, batch run and findings.
What it looks like
Companion View
custom extension - see below for download package and installation instructions
A small extra we built on the side: a browser page of the Reqtify graph, one card per document, the whole chain highlighted when you point at an element, coverage per document and a gaps-only filter. Show in Reqtify selects the element in the Reqtify window, Show in Jira opens the issue, and Show in CATIA Magic jumps to the element through a bridge plugin, since the Teamwork Cloud coupling has no navigation of its own. It is a prototype, built on Reqtify's script hooks, and it is in the package below.
Files
- Slides (PDF): the three use cases, the installation, and one architecture-and-scenario view per use case.
- JIRA Integration package (zip): the customised Reqtify types (Teamwork Cloud, MagicDraw, JIRA with the Covers link), the project generator, the GitLab job, the sample (CATIA Magic model as .mdzip, CSV data, Jira work items, loader and use-case scripts) and the Companion View.
- Setup guide (PDF): nine pages, from the model to the release gate, with a walkthrough of the three use cases and a troubleshooting table.
Companion View (zip): the browser view on its own, with the Reqtify add-on, the scripts and the sample page. Also inside the integration package.
Companion View setup (PDF): three pages, the install steps and the reference of the folder.
Versions used: CATIA Magic 2026x R1 with Teamwork Cloud, Reqtify 2026x Refresh1, Jira Cloud, GitLab CI with a shell runner.
Try it and let us know, we would like to hear which use case you started with.
