Determine if a resolved issue is in a given environment?

[laphroaig]

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?

[Brent Villalobos]

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.

[laphroaig]

Is there a JQL clause / field to query issues by builds? Our testers are very lazy.

[laphroaig]

I mean busy.