Page refresh closing edit screen and attachments

Robert de Groot

Hi

My jira pages keep on refreshing.

We use a lot of .pdf attachments and don't want to download them every time we want to view them so we just view them by clicking on them from the view issue screen

The problem is that every time the page refreshes it closes the view of the attachment and we have to re open it which is annoying as we then have to find where we were and some attachments are about 30 pages long

 

Is there a way to disable the automatic page refresh or preferably just get it to not close any attachments we might have open?

 

**Note:  that this is experienced across multiple browsers and I don't experience any other sites refreshing automatically so I don't believe it to be a browser issue

Earl McCutcheon

Hi Robert,

Jira does not natively have an auto page refresh capability, the data should be static when viewing an issue to prevent the behavior you are describing.

Possibilities here could be that there is either javascript injected in the announcement banner or a field description triggering the refresh or it has been added in as a web resource in a plugin.

Check the announcement banner for javascript input and then you can run the following Query in the DB to check for and scripts injected from a custom field to narrow it down:

select * from customfield where description like '%<script%' or description like '%<script%';
select * from fieldconfigscheme where description like '%<script%' or description like '%<script%';
select * from customfield where description like '%avascript%' or description like '%html%' or description like '%css%';
select * from fieldconfiguration where description like '%avascript%' or description like '%html%' or description like '%css%';

Alternatively it could be a Add-on triggering the action (example of what it would look like here), and this could be a bit more difficult to track down, Recording a web session and reviewing the HAR data would be a good start details on how to do this can be seen here, or disabling add-ons one at a time until the behavior stops.

Regards,
Earl