I was trying to create an Automation Rule which will log the work once the status transitioned. For example, from "In progress" to another status. However, it shows me this type of error.
Hi @Muhamad Aliff Bin Sabri -- Welcome to the Atlassian Community!
You note seeing an error, and I do not see an error in the image you posted. What are you seeing that is not working?
Best regards,
Bill
Good day @Bill Sheboy
The objectives is to show a time spent per status by having a minus of Now() and time when timer start ticking. I try to force log work in every issue transitioned by having above formula. But I was getting this error instead.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you just need to see time in status, I recommend instead using Jira's version of the control chart: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/
If you still want to log the time instead, I do not believe you can query the prior worklog entry to find that difference. Instead you might need:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
If a custom field need to be created, what is the correct way to do it to keep the time track?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe I noted the steps you need above. Please look here for more information about the date/time diff() calculations: https://confluence.atlassian.com/automation/date-and-time-functions-993924864.html
What have you tried so far? If you have your updated rule, please post that so the community can offer suggestions. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Muhamad Aliff Bin Sabri
If you are doing this for cost tracking, I don't recommend creating worklogs based on workflow transitions since it will probably produce inaccurate data. People usually don't work in a first-in-first-out manner so worklogs will just show you status time, which will be different the actual time spent on it. Status time data is already available in each issue's history. Also, your automation rule will not consider your working hours while creating worklogs so the results will probably be even more inaccurate.
In case you are OK with using a marketplace app, 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. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Resolution Time, Cycle Time, or Lead Time.
The app has custom calendar support so you can report on status durations based on your working hours (excluding non-working hours and weekends)
You can calculate averages and sums of those durations grouped by the issue fields you select. (For example, see the total InProgress time per Epic or average Resolution Time per issue type).
The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.
Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.
Using Time in Status you can:
https://marketplace.atlassian.com/1211756
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.