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

Filtering by custom field - no matches for a specific project

carolina_z15ajl

Hello!

I created a custom field type (Account Name) with 500+ values, and made it a global field so I could use it on my team-managed project.

Since my team-managed project's issue types are all specific to that project, they don't show up in the "Choose Applicable Issue Types" list in the Modify configuration scheme context page, so I selected "any issue type", see a screenshot below.

Screenshot 2023-03-17 at 14.20.45.png

Everything works fine, I added the custom field to all my issue types in the project.

I then wanted to filter my issues by Account Name, and when I added this field, still, everything worked fine, you can see that it returns 2 tickets - #148 belonging to my project. Screenshot 2023-03-17 at 14.22.19.png

But if I try to apply the filter only to my project (instead of having project:all), a weird message pops up saying that my value is not valid in my current project or issue selection?

Screenshot 2023-03-17 at 14.27.54.png

I've even tried to first select my project and only then filter by the Account Name but no matches show up...

Screenshot 2023-03-17 at 14.31.39.png

I find this to be weird, if one of my tickets for my project shows up when I filter by account name, why won't it show up when I filter it again adding that it should belong to my project?

Thank you!

Accepted answers

Oday Rafeh_2jhprw

Hi @carolina

It seems like the issue you're facing could be related to Jira's indexing or a bug with the JQL query. Here are a few troubleshooting steps you can try:

Re-index your Jira instance: Sometimes, Jira's search index might be out of sync with the actual data, which can lead to unexpected search results. To re-index, go to Jira Administration > System > Indexing and click on "Re-Index."

Check the field configuration for the project: Ensure that the custom field (Account Name) is correctly configured for your team-managed project. Go to Jira Administration > Issues > Custom Fields, locate the "Account Name" custom field, and verify that it is correctly associated with the project and issue types.

Simplify your JQL query: Try to use a simpler JQL query to filter your issues. For example, use the project key and the custom field ID in your query:

project = "YourProjectKey" AND "customfield_XXXXX" = "YourAccountName"

Replace YourProjectKey with your project key, customfield_XXXXX with the ID of the custom field (Account Name), and YourAccountName with the account name you want to filter by.

Verify user permissions: Ensure that the user performing the search has the necessary permissions to access the custom field, issues, and project in question.

All comments

Oday Rafeh_2jhprw

Hi @carolina

It seems like the issue you're facing could be related to Jira's indexing or a bug with the JQL query. Here are a few troubleshooting steps you can try:

Simplify your JQL query: Try to use a simpler JQL query to filter your issues. For example, use the project key and the custom field ID in your query:

project = "YourProjectKey" AND "customfield_XXXXX" = "YourAccountName"

Replace YourProjectKey with your project key, customfield_XXXXX with the ID of the custom field (Account Name), and YourAccountName with the account name you want to filter by.

Verify user permissions: Ensure that the user performing the search has the necessary permissions to access the custom field, issues, and project in question.

carolina_z15ajl

Hello Oday,

Thank you for your quick reply!

1. Re-index your Jira instance - I can't seem to find the Re-index option, I went to advanced settings, project settings, system and there is nothing under that name

2. The Account Name is associated to 1 project and I can confirm it's mine + "this field will be available on issues of any type in all projects".

3. Simplify your JQL query: this worked!!

project = CS_Customers AND "Account Name[Select List (multiple choices)]" = "Gongos"

However, when I switched to the basic search the red exclamation mark appeared again:

Screenshot 2023-03-17 at 15.12.14.png

4. Verify user permissions: Yes, I'm an admin

Given that with JQL the results come up, could this be a bug? And if so, do you know how I can report it?

Patricia Francezi_iDev_

hI @carolina

As per your question

I created a custom field type (Account Name) with 500+ values, and made it a global field so I could use it on my team-managed project.

Can you share you request / issue type screen pointing to this "global" field?

THe global fields are not available for usage in team-managed projects.

I wonder how you used it in your project...

Currently the fields created under team managed projects can be used by other team managed projects, but thats all.

Oday Rafeh_2jhprw

Hi @carolina

I'm glad to hear that simplifying the JQL query worked for you. It's possible that the issue you're facing with the basic search is a bug or limitation in Jira's search functionality.

To report the bug or ask for further assistance, you can contact Atlassian Support:Visit the Atlassian Support Portal: https://support.atlassian.com/ .
Click on the "Contact support" button.
Log in with your Atlassian account or create one if you don't have one.
Select the product you need help with (in this case, Jira Software).
Fill in the required information, such as the URL of your Jira instance, the version you are using (if applicable), and a description of the issue you're facing.
Provide relevant screenshots or logs that could help diagnose the problem.
Submit the support request.

Atlassian Support will get back to you with a response or a possible solution to the issue.

Regarding the re-indexing option, if you're using a Jira Cloud instance, you don't have direct access to re-index the entire Jira instance. Re-indexing on Jira Cloud is handled automatically by the system. However, if you believe that the indexing is causing an issue, you can mention it in your support request, and the Atlassian Support team will be able to investigate further.

If you want you can try the following alternative solutions:

Create a filter: You can create a filter using JQL and save it for future use. To create a filter, go to "Issues" > "Search for issues" > switch to "Advanced" mode, and then enter your working JQL query. Once the query is set up, click "Save as" to save it as a filter. You can access your saved filters by going to "Issues" > "Manage filters."
Create a dashboard gadget: You can create a dashboard gadget that displays the filtered issues based on your JQL query. To do this, go to your dashboard, click "Add gadget," and choose the "Filter Results" gadget. Configure the gadget to use the saved filter that you created in the first step.
Use a browser extension: Some browser extensions, like Jira Assistant for Google Chrome, provide enhanced search capabilities and additional features that can help you filter and manage issues more efficiently.

Please note that while these alternative solutions may help you work around the issue you're facing in the basic search, they may not resolve the underlying problem

carolina_z15ajl

Thank you so much for all your help!

carolina_z15ajl

Hi! Global fields can be used in team-managed projects here is more info: https://community.atlassian.com/t5/Jira-Cloud-Admins-articles/Announcing-the-ability-to-re-use-global-custom-fields-in-team/ba-p/2209113

Patricia Francezi_iDev_

Good - didnt know - thanks for sharing

Patricia Francezi_iDev_

Just to add something here

Currently this is not totally live for all customers - so thats why i dont have this in my instances.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud