We have a test environment which is built periodically upon tester demand. An issue may have been committed and resolved by a developer, but not yet built and deployed to the test environment. By what means do JIRA / Bamboo / Fisheye admins allow the testers to easily determine if a resolved issue is represented in their test environment?
If your Bamboo plans retrieve source code from a repository, then each build should list the changeset (files, authors, and comments) since the last build. If those comments contain Jira ticket keys, then those keys will be listed in a "JIRA Issues" section of the build along with their description and status. And depending on your setup, if you go to a Jira ticket it will list all the Bamboo builds and Crucible reviews that reference that ticket.
Now, it would be up to you to come up with a way of suck up that info (much of it is available via the REST interface) in a way that makes sense for your environment.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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