Jira and Google Drive, nothing for requirements
Already in use
- Jira
- Google Drive (planned)
Added with ALM OS
- ReqManTool · free
- Test results · paid
- Documents · paid
Starting point
A product team plans and tracks its work in Jira and keeps specifications and plans as files on Google Drive. Requirements live in documents and spreadsheets; test results stay in CI.
What is missing
No managed requirements, no link from a requirement to the Jira story that implements it or the test that verifies it, and no frozen record of what was released.
Licence
Free: the core, ReqManTool (up to 5 modules), sign-in, My work and the calendar. Paid: Jira, Test results and Documents.
How ALM OS fills it
- ReqManTool, inside ALM OS, holds the requirements and test cases: modules, attributes, links, ReqIF and Word export.
- The Jira plugin reads epics, stories, tasks and bugs — and Xray or Zephyr Scale tests, if the team uses them. New issues can be created in Jira from ALM OS.
- The Test results plugin reads the JUnit XML or Robot Framework files the CI writes.
- Documents keeps the controlled versions of plans and specifications. A Google Drive plugin is planned; until it is available, the files that need control are uploaded to Documents (whole folders can be dragged in).
- People sign in with Google Workspace through OpenID Connect; their meetings come into My work from Google Calendar’s secret iCal address.
What they gain
- Each requirement traced to the Jira stories that implement it and the tests that verify it, with the coverage and the gaps in one matrix.
- The links appear in Jira as remote links, so developers see the requirement on the issue.
- When a story or a requirement changes, its links turn to Needs review.
- One release baseline across ReqManTool, Jira, the test results and Documents, signed off by independent people, with an evidence report for the assessor.
- My work lists each person’s Jira issues and requirement reviews next to their meetings.