As a requirements manager I want the traceability report to mention the GitHub location of each item which comes from a file inside a git repository (hosted on my company's GitHub Enterprise server), so that I can - map the traceability report to a commit SHA, and - easily navigate to the corresponding location.
The location shall include: - the full URL including the git commit SHA, - and the line number (if applicable).
Note: - The assumption is that, the repository will be checked out locally by the user or CI system, and the URL to the remote repository will be given as input to the LOBSTER tool suite. That is, the tool suite does not have to detect the commit SHA on its own. - The line number is optional, because otherwise it is impossible to represent files as a whole by a LOBSTER item.
Issues:
missing reference to System Requirements
Build Reference: main | Timestamp: 2026-10-19 07:48:19+00:00 UTC
As a CI administrator I want that the tool exits with a non-zero return code whenever it encounters invalid input so that the CI pipeline can catch invalid input automatically.
Issues:
missing reference to System Requirements
Build Reference: main | Timestamp: 2026-10-19 07:48:19+00:00 UTC
As a user of LOBSTER I want to have a good usability and standard command-line ergonomics, like built-in help or automatic creation of output destinations, so that using the tools is intuitive and seamless in scripts and interactive use.
Issues:
missing reference to System Requirements
Build Reference: main | Timestamp: 2026-10-19 07:48:19+00:00 UTC
IF the provided repository root directory contains a ".git" directory, THEN the tool shall write the output in the LOBSTER interchange format to the file given in the "out" parameter.
Issues:
missing up reference
missing reference to Software Requirements
missing reference to System Tests
Build Reference: main | Timestamp: 2026-10-19 07:48:19+00:00 UTC
IF an item in the input report has a file location AND the file is inside the repository given by "repo_root" AND the file is not inside any Git submodule of that repository, THEN the tool shall write, as the "commit" entry of the location of that item in the output file, exactly the value of the "commit_id" attribute of the configuration file.
IF an item in the input report has a file location AND the file is inside a Git submodule of the repository given by "repo_root", THEN the tool shall write, as the "commit" of the location of that item in the output file, the commit SHA of that submodule as recorded by the repository given by "repo_root" AND shall ignore the value of the "commit_id" attribute of the configuration file for that item.