The development team uses Jira to track their work. Developers are expected to add estimates to most tickets. However development time is only part of the overall time to close tickets - QA time is equally important, and in many cases may be much longer than development time. We would like a way to estimate development and testing time separately rather than chucking it all into a single bucket. Logging time should be separate so we can track dev vs QA time separately and easily.
We thought about this approach and ruled it out long ago.
The first problem is this would double our ticket set. The second problem is that someone would have to create EVERY ticket for testing. The third problem is we have dev estimates on subtasks, so then we would need additional subtasks to pair with the existing dev subtasks, which would make management EXTREMELY painful.
So the more I see how Jira is used (in an Agile, and particularly Scrum manner) the more uncomfortable I am with the number of tickets that get generated. One little feature could have 10 or more tickets associated with it, stories, tests, etc. Aie dios mio.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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