Planning and user stories

Speedwave supports work across the whole development life cycle, starting with planning and turning requirements into user stories. That planning step is not a separate tool bolted onto Speedwave. It runs through the same delivery-system integrations that carry your team’s issues, sprints, and project documentation: Atlassian for Jira and Confluence, and Redmine for teams that run their own instance. This is about where requirements live before a session starts; for how a session turns an approved plan into reviewed, tested code, see the default development workflow.

Working requirements into Jira and Confluence

When a project connects Atlassian, Speedwave gets 22 Jira tools and 13 Confluence tools. On the Jira side that covers searching, reading, creating, and updating issues, moving them through transitions, assigning them, adding comments and worklogs, and attaching files from the project, plus Agile work: listing boards and sprints and moving issues into a sprint. So turning a requirement into a user story can mean creating the Jira issue, writing its description, and placing it on the right board and sprint, all in the same flow.

Issue descriptions and comments accept plain text, which Speedwave converts to Atlassian Document Format, or a raw ADF body for richer formatting like links or bold text.

On the Confluence side, Speedwave can search, read, create, and update pages, and add comments and labels, covering requirements, specs, or planning notes alongside the issues that track the work, with page bodies as plain text or storage-format markup.

Working requirements into Redmine

Teams running Redmine get an integration scoped to one project once you set one during setup, so Speedwave works within that project’s data. The Redmine integration has 23 tools covering issues, time entries, journals, users, projects, and relations between issues. On the issue side that includes creating and updating issues and adding comments, which is what turns a requirement into a tracked piece of work.

Redmine fields such as issue descriptions, notes, and comments are Textile markup, not Markdown, so Speedwave writes Textile when it sets or edits them. Status, priority, tracker, and activity values are project-specific numeric IDs in Redmine. Speedwave looks these up through the integration’s stored mappings rather than guessing them, since the same category name can map to a different ID on each instance.

Choosing between them

Both integrations are enabled per project, so a project turns on the ones its delivery process actually uses. Atlassian works with Atlassian Cloud only. Redmine supports self-hosted and on-premise instances, which makes it the fit for teams that cannot use a cloud-hosted tracker. See the Atlassian and Redmine pages for setup steps and the full tool list for each.