We have multiple BitBucket repos and multiple Jira projects. The Bitbucket repos and Jira projects tie up. Each project runs its own sprints.
Often an epic requires work for multiple projects, but the "owner" ends up creating all the tasks for their sprint.
So, say an epic like "Table Service" comes along that requires work in Epos, API, DB. Rather than producing issues in each Jira Project so it can be put into the appropriate sprints, they create all the issues in their project. The team is just about managing to understand this (as we are all still learning), but our growth is making this impossible to keep track and we are getting branches failing as they are behind on master when their review takes place, or being released out of order as the issue is non-blocking, but there's a mismatch between the end result of the 2 branches, etc. Basically problems of many natures!
What we would like to do is to have a way to enforce the relationship between an issue and a repo, and to enforce that only 1 branch for the related repo can be created for an issue.
I'm hoping there is something we can do in the workflow within Jira to enforce this.
Essentially, the epic/story describes what we are expecting of the developers. The issues are the units of work for a single repo and are put into sprints for the appropriate teams.
Being able to enforce 1 issue, 1 branch will help us move to a CI/CD environment.
Currently, I am doing this all by hand as we don't have confidence in the setup and no way to enforce the setup and then have tooling work from that enforced setup.
