Service Hour Tracking

Kevin Hower
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 5, 2024

We're implementing a system to track the utilization of additional service hours purchased by our customers. We've chosen Jira as our primary tool for this purpose and have created a new field to capture the number of hours consumed by each task. However, we're facing challenges in automating the calculation of remaining service hours for each customer.

Our current approach involves manually entering the total number of purchased hours for a customer. Subsequently, we manually deduct the hours used in each task from this total to determine the remaining balance. This manual process is time-consuming, prone to human error, and lacks real-time visibility into the remaining hours.

We aim to streamline this process by automating the calculation and updating of remaining service hours. Ideally, we'd like to:

  1. Centralized Storage of Purchased Hours: Establish a centralized repository within Jira to store the initial number of purchased hours for each customer. This could be a custom field in a specific issue type or a dedicated project.
  2. Real-time Tracking of Used Hours: As tasks are completed and hours are logged, the system should automatically deduct these hours from the customer's total purchased hours. This could be achieved through a workflow transition or a post-function script.
  3. Dynamic Display of Remaining Hours: The remaining service hours should be displayed prominently on relevant issues, such as customer support tickets or project tasks. This could be implemented using a custom field or a calculated field that dynamically updates based on the used hours.

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events