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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.