I hide a customfield from all screens through field configuration which my project use. It will be hiding correctly on screen and immediately I modify some fields in my issue and do update. Now the issues which were visible earlier not shown in issue navigator.
@jannu,
please see this query , if it might help you : https://answers.atlassian.com/questions/238266/does-jql-work-for-hidden-text-custom-field-in-jira
Could you tell us what the JQL is for the issue navigator?
It sounds like your JQL is selecting issues based on the fields you have hidden, so it makes sense that they'd be dropped.
As an example, if you have a field "colour", your JQL says "colour = red" and then you hide the "colour" field in project X then JQL will be going "oh, well, issue X-123 doesn't have field colour, so it's not selected" - doesn't matter if you've got data for the field already, you've told Jira the field isn't there for that project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi Nic,
I displayed issues which belong to a particular project in JQL and no other search criteria placed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm sorry, that does not tell us anything.
Could you post the JQL you are using?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
project = OurProject
the above is the query.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, now try "project = OurProject and issuetype = X" (where X is a single issue type and the query will return at least one issue)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes I tried for Bug issue type and issue navigator search yield no issues but there exists 3 issues with Bug type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Bharadwaj,
try unhiding the field and remove it from screen. And the associate the field to 'bug' issutype.
on search , the issues will appear.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Right, now you need to make sure that the field
a) exists for bugs - check the field context in the list of custom fields
b) is shown for bugs in that project - check the field configuration
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.