The OpenFastTrace IntelliJ Plugin 0.10.0 is now available. This release introduces specification item status filtering to OpenFastTrace run configurations, giving teams finer control over which lifecycle states are included during traceability analysis.

# Item Status Filtering

OpenFastTrace supports four specification item lifecycle statuses:

• Draft: Work-in-progress items under active drafting.
• Proposed: Items that have reached maturity and are ready for approval review.
• Approved: Accepted specifications (the default state for items without an explicit status).
• Rejected: Discarded or superseded requirements retained for historical completeness.

In standard OpenFastTrace workflows, only approved items are traced against architecture and implementation, while non-approved items are treated as informational. However, depending on review workflows and specification phases, developers and reviewers often need to trace draft or proposed items before formal approval.

The OpenFastTrace IntelliJ Plugin 0.9.0 is now available. Following the Test Runner UI introduced in version 0.8.0, this release streamlines project setup with specialized run configuration templates, clarifies defect reporting by distinguishing direct and transitive defects, and upgrades the bundled OpenFastTrace core to 4.9.0.

# Run Configuration Templates

To simplify setting up traceability, version 0.9.0 comes with specialized run configuration templates.

When creating a new OpenFastTrace run configuration (Run | Edit Configurations... | + | OpenFastTrace), you can now choose from four pre-configured templates:

OpenFastTrace 4.7.0, codenamed “Gherkin Importer”, is now available. This release introduces direct support for Gherkin .feature files as specification sources and enables requirement coverage within Markdown and reStructuredText (RST) comments.

# Gherkin Specification Import

The most significant addition in this release is the ability to import specification items directly from Gherkin .feature files. This allows teams using Behavior-Driven Development (BDD) to integrate their executable specifications directly into their traceability matrix.

We are pleased to announce the release of OpenFastTrace 4.6.0, codenamed “Status Filter at Import”. This release introduces a highly requested filtering feature, improves the user interface of our reports, and expands our import capabilities.

# Filtering Specification Items by Status

A major new feature in this release is the ability to filter specification items by their status during the import process. Using the new -w or --wanted-statuses command-line parameters, you can now specify which statuses should be included in the trace.

The OpenFastTrace IntelliJ Plugin 0.8.0 is out. While version 0.7.0 made OFT runs configurable, this release focuses on how you interact with the results.

# Test Runner UI Integration

The most significant change is that OpenFastTrace results now integrate directly with IntelliJ’s built-in Test Runner UI. Instead of scanning a text report, you get a structured tree of results.

This integration provides several benefits:

• Visual Feedback: Results are grouped by source file, specification item, and trace link. Clean items show as passed, while defects appear as failures.
• Deep Inspection: You can expand source files to see affected items and inspect incoming/outgoing trace links as sub-tests.
• Contextual Information: Item IDs, link status, and defect explanations are visible in the test details.
• Easy Navigation: You can jump from result nodes directly to the source files, specification declarations, or coverage tags.

The global Tools | OpenFastTrace | Trace Project action and new run configurations use this UI by default. If you prefer the raw report, you can still opt into the plain text output in the run configuration.