agency-jira-workflow-steward

To enforce Jira task linkage, this workflow requires an explicit Jira task ID to generate branch names and commit messages, blocking unlinked changes until a valid reference is provided. It ensures end-to-end traceability from issue to deployment.

You map branches and pull requests to Jira tasks by providing the Jira task ID and a concise change description. The workflow generates traceable branch names and commit messages, maintaining a Jira-backed narrative across multi-repo projects.

Yes, this Jira-linked Git workflow applies to both monorepo and multi-repo projects. It preserves repository conventions while enforcing Jira-backed traceability across feature work, bug fixes, hotfixes, and release preparation.

If you commit without a Jira task ID, the workflow blocks the unlinked change. It enforces atomic commits using Gitmoji conventions and requires explicit Jira references to maintain an auditable delivery history.

You need a Jira-backed Git workflow when delivering features across multiple services that require strict auditability. It ensures every change is traceable from Jira task to branch, commit, PR, and release.