In our setup, we have three repositories on Bitbucket: two for documents, one for the source. However, a ticket with the issue subtype documentation might actually involve a code change in any (or all) of the three.
It looks like the Create Branch link creates a branch in the source repo associated with the project...which is usually not the repo the documenter has to touch. Hence, the Create Branch link is useless for me, as the documenter.
Do not question or rail against the setup; it is a given, inherited from the Before Times (that is, before I joined the team).
This create branch feature of Jira works very well for the coders. It works passably well for the testers. It does not work for the documenters.
So the questions are:
I have a workaround ("Create the branch manually"). The default is acceptable to most of the team. That link, though, it taunts me so, and if I hit it, I create needless complications.
If nothing can be done, hey, that's life. However, I'd feel foolish if I didn't check.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events