We are currently running test cycle 1 of 5 for our global software product. We need to use the Zephyr dashboard gadgets to get a graphical overview/status of how the tests are being executed.
We are having problems with the Test Execution Burndown gadget, as it seems it is using a start date that is not related to the test cycle. And the strangest thing is that it sometimes works, and sometimes doesn't.
Here's how we have set it up:
Here's how it looks when it works:
And when it doesn't:
All test cycles called "RT - TC1 x" have a from date 15.09.2014, while the gadget seems to believe that it should start 01.06.2014.
Is this a bug, or do we need to configure something to make this one work?
Thank you for letting us know about this issue. The same has been reported by some other users also. We are working on this to get into the root cause of it and fix it. We will keep you posted if we get any further information on this.
Also running into this - trying to convince a development/test group to adopt Zephyr for test execution. When you have defects like this that impact the roll up reporting, it becomes that much more difficult to sell.
Does anyone know as to why it works sometimes and others not - i've not figured it out yet, but we got the burndown working for 2 days consistently, then back to the vertical line mode - from what i can tell, nothing was changed with the release/cycle.
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...
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