Hello, I have a Jira Workflow Toolbox (JWT) calculated date-time field that I can't get to work with JQL searches. Reproduction steps: * Create a JWT Calculated Date-Time Field * Enter a formula like the following: min(fieldValue({issue.cf10000}, issuesFromJQL("type = 'Bug' AND project = " + %{issue.project.id} + " AND fixVersion in (" + %{issue.fixVersions} + ")"))) * Verify that formula works correctly and is returning a value for at least some issues * Run a re-index * Run a JQL search against the new field, such as "cf[10001] IS NOT EMPTY" * No results are returned * Note that the calculated value is displayed properly in issues/search results even though it can't be searched for I have tried background and full re-indexes multiple times with no success. JWT version: 3.1.7

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; } } }

JWT Calculated Field Not Searchable

Jeremy Cupps

Hello, I have a Jira Workflow Toolbox (JWT) calculated date-time field that I can't get to work with JQL searches.

Reproduction steps:

Create a JWT Calculated Date-Time Field

Enter a formula like the following:

min(fieldValue({issue.cf10000}, issuesFromJQL("type = 'Bug' AND project = " + %{issue.project.id} + " AND fixVersion in (" + %{issue.fixVersions} + ")")))

Verify that formula works correctly and is returning a value for at least some issues
Run a re-index
Run a JQL search against the new field, such as "cf[10001] IS NOT EMPTY"
No results are returned
Note that the calculated value is displayed properly in issues/search results even though it can't be searched for

I have tried background and full re-indexes multiple times with no success.

JWT version: 3.1.7

Accepted answers

Sergio García-Consuegra _Decadis AG_

Hi @Jeremy Cupps ,

I hope you find useful the information I'm going to share with you.

These fields are calculated each time they are read. So they are updated in real time.

They have a problem when used with expressions that depends on fields belonging to issues different from current issue, its subtasks, or issues under epic, or under its epic, which is precisely your case, since you are using issues returned by a JQL expression.

The problem is that index associated to this calculated field is only updated when current issue, its subtasks or issues under epic (in case it's an epic) or epic (in case it's under an epic) are updated. So while the calculated field always return the updated value, its index is not guaranteed to keep always updated, and for this reason JQL searches based on this calculated field can return not accurate results.

Our recommendation in order to find calculated fields is using the JWT JQL Functions, which allow you to combine JQL and Logical expressions from JWT.

In this example, I'm searching for calculated date-time (issue.cf13700) field that are not empty and from the project SP.

For this example we used the JQL function issueSelection. You can obtain more information and examples in this page from our documentation.

We recommend you trying this approach and in our most recent release, 3.1.7, which includes several bug fixes that will improve your experience.

Also, we introduced recently we introduced our new Reindex issue action that helps keep custom fields in sync. This action is available for our Automation Rules.

Please let me know if you have any doubt with the proposed solution.

Thank you.

Best regards,
Sergio

All comments

Alex Koxaras -Relational-

Hi @Jeremy Cupps
I didn't manage to reproduce your problem. I created a calculated date time field, but the JQL (is not empty) yield results.

You CF10000 is what field? What values does it have? In order to use that specific calculated I need to know that.

Jeremy Cupps

Hi @Alex Koxaras -Relational-, thanks for your quick reply. The custom field is a Date Time Picker field. I am able to search on that field directly, and I have one issue in my instance with a value for it.

Alex Koxaras -Relational-

I know what the custom field is. But on the formula you have a {issue.cf10000}. What is this field?

And I suppose that cf10001 which you search on the JQL is the date time field correct?

Jeremy Cupps

@Alex Koxaras -Relational- {issue.cf10000} is a custom Jira Date Time Picker field (not JWT calculated field). I think I get the same result with a native field such as {issue.created}, but I'll double-check after running another re-index.

cf10001 that I referenced in "cf[10001] IS NOT EMPTY" would be the JWT calculated field using the formula in my reproduction steps.

Sergio García-Consuegra _Decadis AG_

Hi @Jeremy Cupps ,

I hope you find useful the information I'm going to share with you.

Please let me know if you have any doubt with the proposed solution.

Thank you.

Best regards,
Sergio

Jeremy Cupps

Thanks @Sergio García-Consuegra _Decadis AG_. Unfortunately we plan to migrate to Cloud soon, and custom JQL functions are not available there so we would prefer to avoid that approach.

Your explanation of the problem makes sense; however, the field remains unsearchable even after running a full re-index of Jira. Is this expected, or does this indicate that there is another problem?

Sergio García-Consuegra _Decadis AG_

Hi @Jeremy Cupps ,

Unfortunately, that behaviour is expected, and the only workaround we can offer to you would be using our JQL functions.

Please let me know if there is any other doubt I may assist you with.

Thank you.

Best regards,
Sergio

Jeremy Cupps

I see. Thank you @Sergio García-Consuegra _Decadis AG_ and @Alex Koxaras -Relational- for looking into it.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server

jwt