How do I write a JQL query to list JIRA issues for custom field (Yes/No value)changed between dates

[Rajkumar Rajamanickam]

Is it feasible at all to construct a JIRA JQL query that lists all the JIRA issues updated for a custom field that got changed or created between 2 dates?

The custom field is associated with value "Yes" or "No" 

I am struggling to get one and just wanted to seek help from community. Appreciate any help further. 

[Jack Brickey]

Hi @Rajkumar Rajamanickam , unfortunately history searches are limited to certain system field and cannot be used for custom fields.

excerpt from - jql-operators 

CHANGED

The "CHANGED" operator is used to find issues that have a value that had changed for the specified field.

This operator has the following optional predicates:

• AFTER "date"

• BEFORE "date"

• BY "username"

• DURING ("date1","date2")

• ON "date"

• FROM "oldvalue"

• TO "newvalue"

Note: This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields only.

[Rajkumar Rajamanickam]

Thanks @Jack Brickey  and so I don't have a direct way to construct JQL query for my case then? 

[Dick]

Hi @Rajkumar Rajamanickam

Consider this work-around:

If you have a regular automation that triggers on edits to your custom field and then edits i.e. the Resolution or Fix Version of the issue to a certain value, the changed operator could be used in addition to a poll of that certain value to yield you the desired issues. 

Example: Fix Version would be appended by a CF<number> string. The number part gets updated each time the regular automation is triggered (to make it different than the one before). 

Yes, you would give up normal fix-version usage, and it could hamper you when the usergroup wants to start using fix-version. But it would allow you to query the Fix Version field for issues edited using the date operators. It all depends on your priorities and prerequisites you want to lay down, yours to choose.

Kind regards,

Dick

[Rajkumar Rajamanickam]

Thanks a lot @Dick for your response.

Unfortunately I will not be able to implement this workaround as this will hamper the Fixversion field and the developers/testers will be confused. 

I need to collect this information once ever month. Alternatively, I will live with the manual workaround , going through the history only. 

[Dick]

Hi @Rajkumar Rajamanickam ,

It is always possible to clone the issue to a "control Jira-project" and do the above trick in that project, leaving the original issues untouched. The original issues should be assessable (selectable!) through the linked issue fields. 

Penny for your thoughts on this :)

Dick

[Yuliia_Borivets__SaaSJet_]

Hi @Rajkumar Rajamanickam 

You can check this article: How to see custom field history in Jira

Issue History for Jira might be a good option for seeing changes for the specific custom field. The app is developed by my team. It allows you to filter by dates, projects, etc., and select the custom field.

Here is an example:

[Dan -minware-]

Hey @Rajkumar Rajamanickam if you are open to working with a 3rd party we can help with this at minware. Our tool is able to query against your full change log history with minQL:

(Also works for your custom field)

Disclaimer: we are a 3rd party marketplace provider but there is a free trial so you can check it out with no obligation!