Hi There
We start using Gitflow model for development and branch per issue
The problem we found is how to set up the version in Jira issues once we start the release in Bitbucket without errors.
Let's says we have 10 issues branches already done and merged to develop and decide to start a release/2.0.0 branch: How can we correctly identify these 10 issues to set the version number to 2.0.0 in Jira?
Maybe there is another approach to handle it?
Thank you in advance,
Julio.
References:
https://www.atlassian.com/continuous-delivery/principles/workflows-with-feature-branching-and-gitflow
https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
Sorry for the necro, but I figured it's better to have a late answer than no answer at all.
What we are doing in our project is to plan ahead what features will be included in release 2.0.0, so we manually fill in the Fix Version field in Jira since before the devs start working on the issue.
This further allows us to review the overall progress in meeting the release due date, under the Project Releases screen in Jira.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.