Currently we package a build through our release planning process, and then put it to testing. Due to timeline considerations we get pressed to push the build forward even though all tickets are not fully tested. We are not in production yet so we had a little leniency, and low risk, up until now. We need a way to uncouple the release package if a ticket or tickets don’t pass test, and push the rest of the tickets forward. There were talks of release candidates, putting changes into a master branch and controlling pull requests, and separating resources between development and release, in order to pass audit. Even with a way to pull out tickets that don’t make the test, regression testing on the final package would still need to be considered in the timing, due to the interconnections of code and fixes. I'm looking for a better approach in handling this situation.
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events