You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am trying to use the advanced filter to filter my defects but I am not able to select few customized field as its showing red exclamation mark that
Click on More on the right panel
Search the custom field
Try to click the checkbox
I am not able to select few custom field checkbox and its saying the below issue with RED exclamation mark
"Field is not applicable for current project / or issue type"
Can anyone help in providing the exact steps to resolve this
A field is "not applicable" when the context for the custom field does not place it on that project and issue type.
To make them applicable, go to Admin -> Issue -> Custom fields and go find the missing field. You will see that in one of the columns towards the right, there is a context that specifies projects and/or issue types where the field belongs. If you "configure" the field, you will be able to change that context, expanding it to cover the defects you're filtering on.
Ok, let's try this a different way.
Go to an issue in the Air Canada PSS project and edit it (with the edit button, not in-line), so that you have all the editable fields available. There's no need to change anything for this, we just need to get to a function.
To the top right, there should be a configure button, usually used for showing and hiding fields for the current user's convenience, but there's another option on it called "where's my field?" Use that, and ask it about "Reporter Group". It will pop up a list of reasons why the field is not on the edit screen, with links for admins to fix them. Some of the reasons on there also block fields from being available in search.
I have the same problem, the custom field is an Options Select field. it's has Issue Types and applicable context associated yet not able to pick this field in Search. Doing the "where's my field?" test, it is on the edit screen too. however it's not possible to Search on this field??
Thank you guys! Description of the problem and its solution just helped me :-)
Just putting this out there (maybe it's helpful for others too): I was experiencing a similar problem. In my particular case the root cause seems to have been a permission issue rather than an assignment/restriction issue!
I have an Automation Rule that's supposed to edit a certain field as soon as another field is filled in. However, that rule didn't work, and the Audit Log of Automation stated that it had to do with the field not being available in the project or for the issuetype (which was not the case!).
Solution: The solution seems to have been that the (technical) user we routinely use as the "Actor" for most of our Automation Rules was not assigned the necessary Edit Right in the Permission Scheme of the respective project. As soon as I had assigned the right, the rule worked as expected.
And since that very time, the field has also become available in the search again! Don't ask me why! ;)
We also have the same problem. Here is an example:
Field "Application Found In" is configured in Jira to apply to all projects, but only to the "Defect" issue type.
When using the Basic Issue Navigator interface, and selecting a project with the Defect issuetype and Defects in it with data in their "Application Found In" field, the field is greyed out and cannot be selected. This is true even for querying on just a single project which only has the Defect issue type and no other issuetypes.
This behavior could only be called a bug.
The only workaround is to change the configuration of the custom field so that it's context makes it apply to All issuetypes instead of being limited to just the only one in which it is used. That's a very bad workaround because it completely defeats the purpose of having custom contexts at all. But as far as I can tell, that's the only way to eliminate the error.
The other option is to just use the Advanced interface, in which one would find that everything behaves exactly as it should.