nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to create an automatic rule that will update ticket time fields so that time can be tracked

Yana Nikolayeva_9s3h1a

Hi Team,

I want to create an automatic rule that will update ticket time fields so that when ticket status will change from 'Selected for development' -> 'In progress' start time set to current time and when ticket transition from 'In Progress' -> 'Done' time updated as completed tasks.

I was trying to create a rule with parameters based on ticket Transition status, but was not sure what time fields need to be updated; what custom query code to use to update date time fields?

Can someone help?

Thank you in advance

Accepted answers

John Funk

Hi Yana - Welcome to the Atlassian Community!

Can you share a screenshot of the rule you have so far?

Are doing an edit to the issue set the start time to now()?

Emre Toptancı [OBSS]

Hello @Yana Nikolayeva ,

If you are interested in a ready built solution, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee or group. The app shows the total time spent in a status so reworks and reopens are calculated correctly too.

You can combine statuses into consolidated columns to see metrics like Cycle Time or Lead Time. Also can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average InProgress time per project and per issuetype.). Your question indicates that you plan to use dates for calculating status times but if you need the dates anyway, Time in Status can also list status entry/exit dates.

The app has custom calendar support so you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

Using Time in Status you can:

See how much time each issue spent on each status, assignee, user group and also see dates of status transitions. Get metrics like Lead Time or Cycle Time.
Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
Export your data as XLS, XLSX or CSV.
Access data via REST API.
See Time in Status data and charts for each issue as a tab on issue view screen.

Timepiece - Time in Status for Jira

EmreT

All comments

John Funk

Hi Yana - Welcome to the Atlassian Community!

Can you share a screenshot of the rule you have so far?

Are doing an edit to the issue set the start time to now()?

Yana Nikolayeva_9s3h1a

Was trying to attach file unsuccessfully so will describe my rule setting:

Rule Set Start Date automatically when issue moved into status 'In Progress'

1. When issue transitioned

FROM Selected for Development , Backlog

In progress

2. THEN

Edit issue fields

Start Date

----------------------------

I am not sure if Start Date is a right field to update in this case, same about end date. Should I update some other fields?

Yana Nikolayeva_9s3h1a

Finally was able to upload.

Please do not pay attention to Rule tag ‘Disabled’ as after I did get any result I set it off.

Emre Toptancı [OBSS]

Hello @Yana Nikolayeva ,

If you are interested in a ready built solution, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center.

Using Time in Status you can:

See how much time each issue spent on each status, assignee, user group and also see dates of status transitions. Get metrics like Lead Time or Cycle Time.
Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
Export your data as XLS, XLSX or CSV.
Access data via REST API.
See Time in Status data and charts for each issue as a tab on issue view screen.

Timepiece - Time in Status for Jira

EmreT

Yana Nikolayeva_9s3h1a

Thank you EmreT, it is good to know. I will keep it in mind

Zoryana Bohutska _SaaSJet_

Hi @Yana Nikolayeva

Also, you can try other solutions from Atlassian Marketplace, like:

- Time in Status for Jira Cloud by SaaSJet - lets you view each status duration data and time in groups of statuses. All reports from add-on available for chart view and as the gadget for Jira dashboard.

- Time Between Statuses - calculate status to status time. It lets customize the calculation by setting start/pause/stop statuses and by selection first/last transition to/from status. Additionally using this plugin you can set warming time limits and notification for exceeded issues.

With all this add-on you will be able to monitored Cycle and Lead time.

Hope it helps

Mehmet A _Bloompeak_

Hi @Yana Nikolayeva ,

You can use Status Time add-on. It generates time spent on each status based on a calendar(7/24 or working hours).

If you are looking for a free solution, you can try Status Time Free.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

time-tracking

automation

rule