Now here's the tracking confusion for the BurnDown chart.
- Our organization has two different type of QA one internal (non billable) and performs the testing after development is complete.
- Client QA that performs testing once the ticket is moved to QA (Billable - Client QA).
- Given this scenario with the burndown chart is been created its not showing the correct report (it won't) based on above assumption. so the project managers in here from the different module tend to create a the report manually which is not an efficient choice.
- Is there any configuration in jira in which the dev-QA can e seperate our the dev QA and create the customized report.
No, but you can write a small plugin to generate the customized reports more efficiently.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.