Regarding Simultaneous Scrolling

I can understand this feature request in principle, but how precisely is this supposed to work?
The sizes of the columns in the two tables can be completely different, even when looking at sizes relative to the table width. For example, the first 20% of the first table can correspond to the first 80% of the second table.
So even if we find a way how to compute how far the other table should scroll, this would mean that the two tables would need to scroll at different speeds and one table (the one that the user is currently not scrolling themselves) would even jump around. Furthermore, this would mean that if a user scrolls the first table to the point where they want to have it, and then adjusts the second table, the interesting part of the first table could scroll out of view, with no chance of getting it back without the second table starting to move again. So I suspect the behavior would often be quite frustrating in a way that is worse than the current behavior, where one has to do a little bit more scrolling in some cases, but at least the automatic table scrolling does not work against the user.

If you have a concrete proposal how the UI should interact with the user and how the scrolling behavior should work, we can reconsider this.

Regarding Same Columns

What do you mean here? Columns of setup and statistics table are currently never the same. For each column of the setup table there are several columns in the statistics table.

Two separate tables on summary page #506

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions