Determine if a resolved issue is in a given environment?

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?

1 answer

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.

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

I mean busy.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Jira

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,097 views 0 8
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you