Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Need a new field that tracks the time a ticket spent as Observation type

Tharunkumar B
Contributor
August 27, 2023

Is there a way for us to track the time a ticket as spent as a certain ticket type?

For example when we "move" a ticket from Observation type to FIR, the creation date remains the same but when we export the data we need to remove the time it spent in Observation as that does not count the same as FIR. 

This would be similar to the changes we made in the past that tracks the time tickets spend in certain statuses (watch, on-hold) - I think when exported it is in seconds 

1 answer

1 accepted

0 votes
Answer accepted
Aron Gombas _Midori_
Community Champion
August 28, 2023

The Better PDF Exporter app has a customizable PDF template that is called "time-by-x" (report samples).

It calculates the time spent in a given field value. By default it supports the Status field (time in status use cases), the Assignee field (time by assignee use cases for issues that are passed between assignees) and it has an interesting fall back case. Every other field is treated as "string value". That fall back cases could work for Observation type, out of the box! If not, it may be very easy to adjust for that.

When exported, the template calculates several KPIs and renders 3 types of charts to visualize the lifecycle of the issue:

jira-time-in-status-report.png

(Discl. this paid and supported app is developed by our team.)

Tharunkumar B
Contributor
August 31, 2023 edited

@Aron Gombas _Midori_ ,Provide the list of supported App to install to fix this issue

Aron Gombas _Midori_
Community Champion
September 3, 2023

I don't understand the question.

The sample above was created with this app: https://marketplace.atlassian.com/apps/5167/better-pdf-exporter-for-jira?hosting=datacenter&tab=overview

Tharunkumar B
Contributor
September 4, 2023 edited

@Aron Gombas _Midori_ Imagine you have two types of tasks: "Observation" and "FIR." When you change a task from "Observation" to "FIR," the original start date remains unchanged. However, you want to measure only the time the task spent as "FIR," not counting the "Observation" time. It's like starting a timer fresh for the "FIR" part to see how long it took. This is similar to tracking time tasks spent in stages like "watch" or "on-hold."

Note-issuetype is observation and FIR

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
atlassian, confluence, loom, atlassian intelligence, ai notes, ai-powered meeting notes, atlassian community events, ace, confluence ai, loom ai integration, ai note-taking, atlassian ai features, team '25, atlassian live learning, confluence automation

Unlock AI-powered meeting notes: Join our live learning session! 📹

Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.

Register today!
AUG Leaders

Atlassian Community Events