2 results found
3 votesLucy Holloway shared this idea ·
Thank you! please check the comment
An error occurred while saving the commentLucy Holloway commented
I strongly support this suggestion.
The current justification against it is: "because you can have different monitors and different window sizes, and Structure tries to autosize width for your window."
This is no longer valid. The reasons that this is not valid are outlined here:
The reason that column widths should be saved to views and perspectives is that structure's auto-widths are often not appropriate, and must be re-sized. Your previous justification *used* to be valid, because with no horizontal scrolling, Structure had to auto-size the widths for each window so that the user could always see all of the columns.
However, it is now possible to horizontally scroll, so for any window size, the user will always be able to scroll to see every column in the view.
The current result of the fact that column widths are not saveable is that every user, on their first time using a view in structure, and on their first time seeing a display of a structure in the view in Confluence, must be shown how to re-size column widths, and then re-size each column so that it is of the optimum width. Examples of width changes:
1) Making the Comments (Notes) column extra wide.
2) Making a column that is there so that an issue field is editable, but does not have to be seen, extra narrow.
3) Making certain columns narrower so that the information can still be seen, but the amount of horizontal scrolling a user has to do is minimised.
Extra steps such as this for *every user* make using Structure less favourable, leading employees to prefer other tools / methods.
Doing this once, then saving the widths to the view, would be fantastic
Therefore, please implement this suggestion. Structure has many excellent features and I would like for other employees to come on-board!
LucyLucy Holloway supported this idea ·