Sztab will restore commit-to-issue linking using issue IDs in commit messages, in a Git-provider-agnostic way (but will test it for Forgejo and OneDev for Release 1.7, due to time constraint - but since Sztabina relies on git, there is no reason why this wouldn't work for other git repos).

The linkage will be visible directly on the issue page and won’t depend on how the PR was created. This is a natural extension of Sztabina:

• PRs already reference commits
• Issues already reference PRs

Commits referencing issues complete the triangle

Branch: feature/SZ-pull-request-workflow

Please see: https://tigase.dev/sztab/~issues/55

Resolution Summary — Issue-Commit Linking (SZ-34)

The original request (SZ-34) asked for restoring visibility of all commits related to an issue, inferred via issue IDs in commit messages — functionality previously removed in 1dev and missed in daily workflows.

This has now been functionally resolved through the new Pull Request workflow backed by Sztabina:

• Commits are discovered and compared via Sztabina during PR creation
• Pull Requests explicitly list all associated commits
• Issues are linked to Pull Requests
• As a result, all commits relevant to an issue are visible from the UI via its Pull Request(s)

This approach is architecturally cleaner and more robust than commit-message-only heuristics:

• Issue => Branch => Pull Request => Commits
• No reliance on fragile parsing of commit messages
• Restores and improves the removed 1dev capability

From a user perspective, the core pain point described in SZ-34 is resolved. If needed, the issue can be closed as fixed via PR-based commit discovery or reworded to clarify the PR-mediated linkage.