Custom fields are not displayed automatically.

[Leonardo Zevallos Guzman]

I have created custom fields in JIRA, I have added them to the default schema so that they appear when creating issues in a new project but they do not, I show them graphically.
                                They do not even appear in the display fields/custom fields section.
However, they appear when I already create an incident in this section.

The configuration I made is this:


If someone could tell me the solution with detailed steps, that would be great.

[Udo Brand]

The only operators you can use for component are =, !=, in , not in ,is and is not. So no chance out of the box.

Maybe you could use script runner plugin which has an additional JQL function

component in componentMatch("string.*")

[Alexander Richter]

i want to search for issues that have ONLY a certain component.

1. no component -> issue is not in filter
2. component is MBA and DV -> issue is not in filter
3. component is MBA -> issue is in filter

is there a possibility to do that with a regex expression?

[Nathaniel Irons]

Long after the fact, this looks like it has the intended effect:

component in (MBA) AND component not in (DV)

[Andy Strickland]

I tried several solutions for this myself before I came to one that worked for me.

(component is EMPTY OR component not in ("componentName"))

I wanted to show any component, even if the component is empty. Because of the architecture, the component field does not exist until a component is added to the issue. Therefore, component != or something like this will not work, because the component field does not exist and cannot be parsed, so it will return an empty issue list.

Also, just slamming an OR into your existing JQL will break the rest of your filter, so you have to wrap the whole thing in parenthesis.

Hope this helps someone.

[Filipe]

Hi,

Try if

https://marketplace.atlassian.com/plugins/pt.lt.lfcribeiro.jira.jqlLTFunctions

Solves your problem, nevertheless it will let you run SQL functions using executeQuery()

Regards,