The goal is to allow one resource to enter time with different billing types to the same JIRA issue. So, I might enter an hour to issue XYZABC-1 with a 'Underwater Basketweaving' type of work that ends up translating to a bill rate of x dollars. . Then later that day, I might add an hour of work to XYZABC-1 with a type named 'Nuclear Engineering' that translates to a bill rate of x + 5 dollars.
We've used sub-tasks or different issues to log time against objects that can then be calculated correctly.
I've seen https://marketplace.atlassian.com/plugins/com.adweb.estimations.estimationUpdate/server/overview which seems to be well liked.
We have discussed using different issues as well, but feel that could get difficult to manage. So, a task could possibly have 5 or 6 different types of work that might need to correlate with each other. One for QA, which may need to easily tie back to web dev or SE or creative versions of the same. Suddenly, changing the assignee could become a nightmare.
That plugin is interesting as well. It looks like it is right along the lines of the sort of thing we would want.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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