We are using Jira with both Zephyr and Greenhopper together. I would like to be able to use the chart board for tracking our release progress, but we have to leave our "test case" issue types open for Zephyr. So we wind up with tons of open/in progress issues for the release (the test cases) which makes the release look like it's going very poorly indeed from a burndown perspective.
Our current process is to create a Story with a point estimate, add subtasks for development tasks with time estimates and then link the test case issue to the Story to show the relationship. The QA team also adds subtasks to the story for creating and executing the test case.
Does anyone else use both Zephyr and Greenhopper together? And have you found a way to make them work better together? Or at a minimum, have you found a way to exclude test case issue types from the chart boards?
I have the same issue and it's really annoying.
The test cases should not be in the backlog (we create test cases for regression tests which is never closed since they are allways executed before each release) and an option to hide them from the backlog would be very welcome.
It's very clear that Atlassion is twisting their bugtracking engine inside out to squeese in as many agile plugins as possible, and the result is not allways what you would expect.
Thanks for the tip! :)
I did something similar, a quick filter for our scrum board (in plan mode) which only displays stories, bugs and improvements.
Not a solution though, more of a workaround.
The testcases should not be there at all - looking forward to an update where not everything in jira is an issue... ;)
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot