Bring your requirements with you: ReqIF import and export
Import a ReqIF file from DOORS, Polarion and other tools into a new project or an existing one. Download any view, selection or spec level as ReqIF or CSV with more formats to come. To better support your editing, requirement and work-item bodies gain a formatting toolbar, tables, images, quotes and code blocks, and the requirement list gains range selection and moving several requirements at once.
This release is about making it easier to move to Requiremancer. You can now bring a specification in from DOORS, Polarion or any other tool that writes ReqIF, and take any part of a project back out as ReqIF or CSV for use in third-party tools that support it. To better support the ReqIF standard, the body editor gains a toolbar, tables, images, quotes and code blocks. As a bonus in this release, the requirement list also gets quicker to work through when you are handling many requirements at once.
New and improved
Import a ReqIF file
- Where. Project Settings → Import & export → Import a ReqIF file…, for project admins. To start a new project from one, choose Start from: A ReqIF file under New Project.
- Preview first. Nothing is written until you choose Import. The preview shows:
- what the file would create;
- what it would skip, and why;
- which formatting each body would lose, such as underline, colour or merged cells;
- how much of your requirement quota it would use.
- Choose the mapping. Map each specification in the file to a new or existing spec level. Map each attribute to the title, the body, a custom field, or nothing. Map each relation type to a link type, in either direction. The preview updates after every change. The mapping is remembered for the project and for the tool the file came from.
- How the file maps.
- Headings become chapters, and the other objects become requirements, filed in the document’s order.
- Bodies become Markdown, tables included.
- The source tool’s identifiers are kept in custom fields.
- Other attributes become custom fields, created only when a value lands in them.
- Never overwrites. An object that was already imported is skipped and named, with the requirement it became, and links to it still connect. Existing spec levels, chapters and fields are reused, never changed. Importing the same file twice creates nothing the second time.
- Limits. A file can be up to 16 MB or 50,000 objects, and one import runs at a time per server. A very large project’s own export may not fit yet.
- Tested with files from DOORS, Polarion, ReqIF Studio, Enterprise Architect, Eclipse RMF and StrictDoc.
Download requirements as ReqIF or CSV
-
A whole view. The requirement list and grid each have a Download menu offering This view, as ReqIF or CSV. The file holds every requirement the view’s filters and sort match, not only the rows already loaded, in the view’s order.
-
A selection. The same menu downloads the selected requirements. Right-click a row for Download N selected as, or Download as for that row alone.
-
Whole spec levels. Project Settings → Import & export downloads chosen spec levels, or the whole project, as ReqIF.
-
What a ReqIF file holds.
- One specification per spec level, with chapters as headings.
- Status, priority, type, tags and your custom fields as attributes.
- Links between the exported requirements.
- Bodies in the formatting other tools read. Images are written as their alt text for now.
Two exports of an unchanged project are identical apart from their creation time, so they compare cleanly.
-
Who. Admins, editors and contributors can download. Viewers and guests cannot, and every download is recorded in the audit log.
-
Other grids. Signal, test-case and work-item grids still download only the rows they have loaded, and now say so: “Loaded rows · 200 of 5,000”.
A formatting toolbar for bodies
- Where. Requirement and work-item bodies.
- Controls. Bold, italic, strikethrough, inline code, bulleted and numbered lists, quote, code block, link, and requirement link. The requirement link opens the same picker as typing
[[. - Shortcuts. Each control does exactly what its keyboard shortcut does. New shortcuts: Ctrl+Shift+X for strikethrough, Ctrl+E for inline code, Ctrl+Shift+8 for a bulleted list and Ctrl+Shift+7 for a numbered list (⌘ on a Mac).
- Toggling. A control toggles its format off where the text already has it, and shows as pressed there.
- Fixed. Ctrl+I now makes text italic. It used to select the surrounding text instead.
Tables in bodies
- Inserting. Insert table opens a size grid; pick the rows and columns.
- Editing. Tables are always drawn as tables. Click a cell to edit it where it stands: it shows its own Markdown while you type, and is drawn formatted again when you leave.
- Moving around.
- Tab and Shift+Tab move between cells, and Tab in the last cell adds a row.
- Enter and Shift+Enter move down and up.
- Escape leaves the table.
- Rows and columns. The toolbar adds and deletes rows and columns while you are in a table.
- The source. The table’s Markdown control shows its source when you want it.
- Wide tables scroll inside their own box, so they never widen a panel or a list row.
Images in bodies
- Adding. Use Insert image in the toolbar, paste, or drop a file. PNG, JPEG, GIF, WebP and SVG are accepted, up to 10 MB each.
- No jumping. Each image keeps its space from the moment the body is drawn, so the text around it never jumps as it loads.
- Storage. Images count against your plan’s storage. When storage is full, Insert image says so before you try.
Quotes and code blocks as they read
- In the editor. Quotes and code blocks now look the same as they do once saved. A code block is a monospace box labelled with its language, and its fences appear only while the cursor is inside it. A quote carries its left rule, with its
>shown only on the line you are editing. - When read, a code block is labelled with its language too.
Select and move several requirements at once
- Selected and open. A card open in the side panel now has a soft tint, and a ticked card a clear border. A card that is both reads as one state, not two.
- Shift-click a card to tick every card from the last one you ticked or opened. A plain click still opens the card. The test-case list works the same way.
- Clearing. Escape clears the ticked cards, and a second Escape clears the keyboard cursor. Ctrl+D (⌘+D on a Mac) clears the ticks too.
- Moving together. Drag any ticked card by its handle and every ticked card on screen moves with it, keeping its order. While you drag, the others dim and the drag shows how many are coming. Drop them under another chapter to file them all there.
Fixed
- Organisation owners and admins were refused in several places in projects they manage. The graph said “Requirement not found” when opening a requirement, the Members tab failed to load, and test runs were refused. These now work. The Members tab now lists everyone who can open the project, and says whether each person’s access comes from the project, the organisation or a team.
- People who had left a project could still reach some of its test runs and members.
- Viewers could upload evidence to a test run. Uploading now needs permission to edit tests.
- Filtering requirements by tag through the API, or the
list_requirementstool in the MCP server, failed with a server error.