Legacy issue view (not New issue view): can't scroll when originating from a search results page

[Chris Blessing]

Hi Jira Support Community & Experts,

We are having an issue whenever we aren't using the "New issue view" (Jira Labs) feature.

If you load a particular issue in this legacy view originating from an issue search page, it seems to load and render, but you cannot scroll down. In fact, it's only the issue content itself that won't scroll (e.g. comments area, div#content); the left side bar menu does scroll (div#navigation-app).

If you don't originate from a search page, there's no "Return to Search" link and the issue view scrolls perfectly fine. So to be clear, the problem is only present on issues which display that upper-right corner Return to Search link as far as I can tell.

We've found this an issue across mac and windows, and FF/Chrome/Safari. I'm currently showing the issue in the latest of all three browsers.

Looking into the DOM, I can see the page structure is different based on directly viewing the issue or originating from search results. In particular there's a scroll handler assigned to div.issue-view but no such element or style/event on the search-originating issue page (instead it's div.issue-container). If I had to just guess, I'd say this is the root cause of the problem.

If I mess about in the web inspector a bit, I can get the issue content to scroll by applying:

height: 872px; /* whatever the window height is; should be set on resize */
overflow: auto; /* or overflow-y of course */

If I had to guess a bit more, I'd just say there's a missing call to assign the height on this div.issue-container element when viewing the search-results-originating issue, as well as a missing scroll handler or style.

Is this something we can get fixed in the source, or will I need to add this to our jira instance manually somehow? I am not a jira admin so I'm not entirely sure how I'd go about doing that (yet). We'd like to reliably use this legacy issue view for a bit longer.

Thanks in advance!

~~~ Attachments ~~~

1. Adding CSS to .issue-container fixes the scrolling; height needs to be updated on window resize

2. Stock Jira code with declared height and scroll handler on .issue-view (this is from the directly-linked issue view page, I did not modify this). Also here, height is updated when the window resizes

[Andy Heinzer]

Hi Chris,

Thanks for the detailed post.  I understand that you have found a particular view that is not allowing you to scroll down the page in order to see the complete issue details.  I have been trying to recreate this problem in my own Jira Cloud site, unfortunately so far I have not had any luck here.  For me this just works.  So I'm curious if perhaps the problem is specific to your Cloud site.

I know you mentioned that this was happening when loading the issue from search results.  However that could be done in at last two different URL paths on the site that I am aware of.  For example, you could be in the Issue Navigator, which would have a URL such as [yoursite].atlassian.com/issues/?filter=10016

OR

Some projects also now have a new project specific issue navigator, that tends to have a URL such as [yoursite].atlassian.net/projects/KAN/issues/KAN-35?filter=allissues

I would like to try to clarify if this is happening when the URL in your browser is using one method, or the other, or both.  In my own site, I can't seem to recreate the problem you have described here. I'd be happy to try to investigate this further if I can learn more here.

Aside from the additional problem details, you might want to reach out a member of your team that has the site-admin level permissions for this Cloud site. Those specific users will be able to create a support request directly with our Cloud support team when visiting https://support.atlassian.com/contact I fear that this might be necessary in this case since the problem could be specific to your account or specific to your Cloud site. 

But since your account is not a site-admin there, any questions you post there will just be redirected here to Community. 

Let me know.

Andy