we just recently switched to a feature branch workflow with git. Our infrastructe is based on the atlassian tools jira, bamboo and stash.
All works pretty smooth and all three tools share their status. I can create a branch named like a jira ticket and trace its complete workflow through jira and bamboo until it is released.
But there seems to be one important missing feature: We often have the situation, that a jira ticket has plenty subtasks or some linked tickets. There will be no seperate branch for all the referened tickets, all commits go directly into the parent branch.
This is where we loose traceability of the subtasks, there seems to be no way in jira to see in which branch a referenced ticket has been resolved.
We need to know, which branch contains commits for certain tickets. When I have this information, I can deploy the branch for QS and present a list of all the new features/fixes that have been resolved in this branch.
Do you have similar problems or how would you solve this?
You are right, the JIRA Ticket will only be updated when it is mentioned in a commit message. We do mention all our subtasks in the commit message, but this does not solve the problem. When we do this, JIRA shows the commit but there is no information that this commit exists only in a branch.
So we still dont have a list of all the commits or resolved issue in a certain branch.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs