Roadmap

Last updated: 2026-04-27

This page reflects what ubConnect ships today, what is in progress, and what is planned. Each entry is tagged with a status.

Legend

  • Shipped — available in the latest release.

  • In progress — actively worked on.

  • Planned — committed in principle, no implementation yet.

Connectors

ReqIF

Shipped

  • reqif to-reqif — export Sphinx-Needs to .reqif / .reqifz.

  • reqif from-reqif — import .reqif / .reqifz into Sphinx-Needs.

In progress

  • Hierarchical relationship extraction on import (parent_need, children, level).

  • Round-trip fidelity for the DOORS NG pipeline.

  • Multi SPEC-OBJECT-TYPE support via type_field, hierarchy_field, and [[object_types]] on import.

Planned

  • to-reqif: include need RST content in the export.

  • to-reqif: export attachments.

  • to-reqif: mapping configuration via CLI options for Bazel integrations.

  • from-reqif: HTML-to-RST conversion for rich-text fields.

DOORS NG

Shipped

  • doors-ng from-doors-ng — import IBM DOORS Next Generation artifacts to Sphinx-Needs.

Planned

  • Import links/relationships between DNG artifacts into Sphinx-Needs link fields.

  • Preserve module hierarchy and document structure (sections, parent-child relationships).

  • to-doors-ng — export Sphinx-Needs back to DNG (create/update artifacts) with config-driven field and type mapping.

Jama Connect

Shipped

  • jama from-jama — import items from Jama Connect into Sphinx-Needs.

  • jama to-jama — export Sphinx-Needs to Jama Connect.

  • jama list-types — list available item types from a Jama instance.

  • jama check — validate connectivity and credentials.

CSV

Shipped

  • csv from-csv — import a .csv file into Sphinx-Needs.

  • csv to-csv — export Sphinx-Needs to .csv.

GitHub

Shipped

  • github from-github — import GitHub repository issues into Sphinx-Needs.

  • github validate-issue-refs — cross-check :issue: references on existing needs against the GitHub issue tracker.

Codebeamer

Planned

  • Import and export via the Codebeamer API.

Jira

Shipped

  • jira from-jira — import Jira issues into Sphinx-Needs.

  • jira to-jira — create Jira issues from needs, with a configurable issue template and a back-link to the exported need.

  • jira refresh-status — read the Jira status of exported issues back into a needs.json.

Planned

  • Updating an already-created Jira issue when its need changes; to-jira is create-only today.

Polarion

Planned

  • Polarion ALM integration.

File formats

Planned

  • Excel.

  • SysML v2.

Cross-cutting

Ontology

Planned

Schema-aware exchange of typed extra options, including support for exhaustive enumerations.