I use JIRA to manage the workflow to a software development team. Once my team is finished coding and testing, we send certain requests to a separate DBA group which implements table changes in the production environment. All of our work for a particular release is managed in one fix version. For example, we might have a fix version called "January Release - Feature XYZ."
The dev team opens, resolves, and closes its JIRAs before the release date. However, the DBAs often leave their JIRAs "in progress" until 2-3 days after the release. This means that our burn down chart for this fix version (not to mention the Road Map gadget for upcoming fix versions) is lways in the red - and we always look as though we're behind schedule.
Has anyone else dealt with a DBA group that left assignments "in progress" until after the release date? How do I deal with this?
There isn't a super-easy way to resolve this, but you can bulk-close all issues in a release;
The bulk operations are performed on the result set of a search, so you could search for all unclosed DBA tickets and then close em up.
Or you could bust out the whip on the DBA team ;)
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
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