Attachment hide from issue

[Marzi Goodarzian]

Hello

My attachments in issues of jira hide from Attachment section, but these show in attachment icon in comment section.

|Why this event happend?How fix it?

thanks

[Nic Brough -Adaptavist-]

Could you explain this a little more please?  I can't work out what you are seeing or what you expect!

[Marzi Goodarzian]

Hello @Nic Brough -Adaptavist- 

all attachments in issues hide from attachment section(attachment section is empty:fig1), but attachments of issues are found in comment section(fig2), like this photos:

fig1:

fig2: attachment is in comment section:

and  before this event, I tried install asset discovery but could not install, Could this be a problem?

this is a critical problem for me :(

thanks

[Nic Brough -Adaptavist-]

Hmm, that is odd.  Is there anything in the logs when you browse the issue?  What happens if you add another attachment to the comment?

[Marzi Goodarzian]

Hello  

In log, this error display:

1- an error occured when performin the gadget feed url healthcheck

2- unable to perform a request to: http://example.com/rest/gadgets/1.0/messageboundle/fa_IR/gadget.comment%2C...

3-error indexing issue DCU-# : Dropping "custom field _10108"

4- Detected Url scheme, 'http', does not match expected scheme 'https'

We use WAF and my language is persian.

when create new project now (software,business or servicedesk) have not this problem!

I got confused,please help.

thanks

[Nic Brough -Adaptavist-]

Ah, right, you have a broken setup. 

Your base url is set to a url that the server running Jira cannot reach.  You'll need to fix the routing and/or SSL on the server to enable it to talk to itself

The SSL is definitely wrong, as you've got SSL set up somewhere (a proxy? maybe your WAF?) but the connector in Tomcat is not set up to support it.

Point 3 is a broken custom field.  You'll need to work out what field 10108 is and fix or remove it from your system (go to the list of custom fields and hover over each ones "edit" link - this will contain a string like id=nnnnn - when nnnnn is 10108, you have the culprit field)