The issuance ticket can also be found in JQL even if the value of issuance ticket in the custom field is not empty "The custom field is empty." This case is caused by an unspecified person. When you click on a related issue ticket, the custom field values are populated, the same JQL search is run again, and the clicked ticket is not exposed. Is this a simple bug? How can I solve this problem?
For reference I am using data center (v.8.13.4)
@Holtzman _김주원_ _BTS Management_ _ - Are you seeing this issue in all the nodes of the datacenter? Try reindexing the project on all the nodes and check again.
Hello, thank you for your reply. @Niranjan
That's right. I'm using a total of 4 nodes and I proceeded with re-indexing for all nodes. However, this problem is still occurring.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Holtzman _김주원_ _BTS Management_ _ - Kindly check if you are using the correct field in the JQL query. There may be more than one field with the same name. Try using the custom field id instead of field name.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Of course, I checked. I confirmed that the exact field name is correct, and that there are no fields that use the same name.
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.