Hi, Community!
I'm trying to gather insights on how often our team updates their Jira issues every quarter, month by month. There are two relevant values: "Status" and "Progress". The field "Progress" is a custom field, which is set to have a value from 0 to 100.
My first thought was to filter using JQL. This is the code that I'm using to filter the issues:
"status CHANGED DURING("2024-01-01", "2024-01-31") AND "progress[number]" CHANGED DURING ("2024-01-01", "2024-01-31")"
This, however, only seems to work when I try to get the status change value, but not the progress fields. Jira returns this message when I try to run the filter:
History searches do not support the 'progress[number]' field.
My second thought was to use a different approach with the following code:
"status CHANGED DURING("2024-01-01", "2024-01-31") AND "progress[number]" > 0 AND "progress[number]" WAS 0 DURING("2024-01-01", "2024-01-31")"
However, I am getting this feedback from Jira:
I am lost here. I've been trying to find many ways to approach this, but nothing seems to work. Am I using JQL wrong? or is this the wrong way to solve this?
If anyone has any other solution, I would appreciate your input
JQL history searches (i.e looking for changes) only works with a small number of system fields, like status - and not with custom fields.
JQL isn't necessarily going to return what you want either - it's going to show you issues which were updated during that month, but not how many times they've done it.
This information is in the issue history though.
A few options are below.
---
Automation:
Given it's only two fields, you could do this...
---
Other:
---
I haven't tried the Automation, but if it's of interest and you need help creating it, let us know :)
Ste
Hi, Steffen! Thank you very much for your input. I'm working on this approach, and if you have any advice on how to set up the automation I would really appreciate it :)
Also, will the query filter work with these new custom fields?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The fields will be available to use in JQL - you'd need to use a different format though. For example, for the date fields it might be...
"Status - Last Updated" >= 2024-04-01 and "Status - Last Updated" <= 2024-04-30
---
In terms of building the rule, this is how I would do it...
Prerequesites
You need to add the fields first. These instructions are for a Company-managed Project, but if it's Team-managed this only impacts the Screen instructions.
You'll need to be a Jira Product Admin, and then...
Once you have the fields created, we'll need the 2 Number Fields' custom field IDs. To get these...
---
Rules
As one of the two fields is Status, 2 rules is better, to allow for the use of two different triggers.
Rule 3 is optional - but is an automated way to clear the data once a quarter.
Rule 1 - Status:
Rule 2 - Progress:
Rule 3 - Clear Data:
---
Notes:
---
Let us know if this works for you!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
JQL supports only six fields within history searches (Assignee, Fix Version, Priority, Reporter, Resolution, Status). It doesn't work for custom fields, so you'll need to look for alternative solutions like those suggested in the previous answer.
If you are ok with third-party apps, check the Issue History for Jira (free for 30 days) developed by my team. It provides the info you are looking for. You can check all the changes made to the field "Progress" or any other.
Here is how it looks for the due date field:
More info: How to get history for the specific issue field in Jira
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.