Hi,
we have written an App which fetches a text from another system into a short text field in Jira. Now we want to be able to filter that field in a work management project. But that field is not visible in filter options, neither in company managed nor team managed projects. So is that due to the fact that it is locked? Or how can i make it "filterable"? I don't want to do something like using an automation to fill a common custom field with that value just to make this possible.
Thanks in advance.
I just found the answer myself. Technically we do a selection from certain values here but we write it in a text field, not a selection. That's the reason why it doesn't appear in filter.
Hi @Tuncay Senturk
Yes it is stored in Jira. I can use it in JQL so it is indexed, that is not the problem. It just doesn't appear in filters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does your app store the text in the field or just fetch and display it in Jira? In order for Jira to index the field, it must have data stored in a way that Jira indexes for searching. We need more clarification (maybe your manifest and code related parts) in order to understand.
Actually, Atlassian developer community might be a better place to ask it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the misunderstanding. Have you checked the issue contexts (Settings > Issue > Custom fields), it may be restricted to a project or issue type which may prevent displaying for unrelated projects or issue types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Tuncay Senturk
No, it is not restricted. As mentioned, it is displayed, i can use it normally in projects, no matter if they are team managed or company managed. I can use it in JQL, works fine. It just doesn't appear in the filter of work management projects. Maybe it is because it is locked? It doesn't appear in portal forms of service management projects as well so there seems to be some kind of restriction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I see, I am unsure that it is because that it is locked as I recall I use locked fields in filters. Sorry, I wasn't helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.