Skip to main content

​
The Problem: Board Scrolls to Top After a Card Update

When you update a card using the side panel, the board may scroll back to the top of the page and lose your current scroll position. This makes it difficult to continue working on boards that require vertical scrolling — for example, a board with many swimlanes or a large number of work items.
In versions of Planningboard prior to the focus-preservation fix, every card save via the side panel triggered a full board reload that reset the scroll position to the top. If you are experiencing this, check your installed version and upgrade if available. See Version Updates and Checking for instructions.
1

Identify Whether Scroll Loss or Infinite Loading Is the Issue

Before troubleshooting, confirm which symptom you are seeing:
Decision flow: after editing a card in the side panel, the board either scrolls back to top (scroll/focus loss issue) or hangs and spins forever (infinite loading issue)
2

Upgrade to a Version With Focus Preservation

The scroll-to-top behavior after card updates was addressed in a Planningboard release that preserves focus on the last edited row after a card update.
  1. Check your current Planningboard version: in Polarion, navigate to Administration > Nextedy PLANNINGBOARD (or your equivalent administration page) and note the installed version.
  2. Compare it against the release notes at Version Updates and Checking.
  3. If an updated version is available, follow the upgrade procedure described in Version Updates and Checking.
After installing an updated version, clear your browser cache and reload the Planningboard page. The board should now return focus to the swimlane row you were editing after you save a card.
3

Verify the Board Reloads Correctly After a Card Save

Once you have upgraded:
  1. Open a Planningboard with enough swimlanes that the board requires scrolling.
  2. Scroll down to a swimlane in the lower half of the board.
  3. Click a card to open the side panel.
  4. Make a change to a field and save.
You should now see the board remain at (or return to) the swimlane row you were editing, rather than jumping back to the top of the page.
The exact mechanism for focus preservation (for example, whether it anchors to the swimlane row, the specific card, or the scroll offset) was not confirmed in the available source context. Observe the behavior in your environment after upgrading.
4

Work Around Scroll Loss If You Cannot Upgrade Immediately

If upgrading is not immediately possible:
  • Use the keyboard: after saving a card, use your browser’s scroll position (Page Down / arrow keys) to navigate back to where you were.
  • Reduce swimlane count per board: consider splitting a very tall board into multiple Planningboard instances, each covering a subset of swimlanes, to reduce the scrolling distance lost on reload. See Configure Swimlanes (Rows) for swimlane filtering options.
  • Filter by Plan range: narrow the board to a smaller set of Plans so fewer rows are rendered. See Filter Swimlanes by Plan Range.
5

Troubleshoot Infinite Loading (Page Never Finishes Loading)

If the board shows a loading indicator that never resolves — rather than scroll loss — the cause is often a network or firewall issue rather than a Planningboard bug.
Infinite loading on Planningboard pages has been confirmed to be caused by corporate firewalls and internal proxies blocking required network traffic. This is not a product defect. The board may appear stuck indefinitely with no error message.
To diagnose:
  1. Open your browser’s developer tools (F12).
  2. Go to the Network tab.
  3. Reload the Planningboard page.
  4. Look for requests that are pending, blocked, or returning non-200 status codes (for example 403, 407, net::ERR_BLOCKED_BY_CLIENT, or long-stalled requests with no response).
  5. If you see blocked or failed requests, contact your network administrator to allow the relevant endpoints.
See Network and Firewall Requirements for the full list of network prerequisites for Planningboard.
Access the Planningboard page from a machine outside your corporate network (for example, via a personal hotspot). If the board loads correctly, a firewall or proxy on your network is the cause.
6

Check the Browser Console for Errors

Whether you are experiencing scroll loss or infinite loading, the browser console often contains useful diagnostic information.
  1. Open developer tools (F12) and go to the Console tab.
  2. Reload the page or reproduce the action that causes the issue.
  3. Look for red error entries or warnings referencing Planningboard resources.
  4. Note the full error message and include it when reporting the issue to support.
Specific browser console error messages produced by scroll or focus issues are not documented in the available source context. If you encounter a specific error message, see Common Errors for general error resolution guidance.

​
Summary

​
See Also

KB Articles
  • Troubleshooting Script Errors in Planningboard
Support Tickets
Last modified on July 9, 2026