You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having added several custom fields to my trackers, I noticed that their overall width is about 50% of whatever parent their are a child of. This is normally not an issue, yet as soon as you start working on a given issue, update its state, attach a revision to it, then those custom fields become very small and difficult to read (especially in case of text-areas).
It would be really nice, if the width could be expanded to 100% of the parent container, whenever a tracker has history and or associated revisions.
The text was updated successfully, but these errors were encountered:
Having added several custom fields to my trackers, I noticed that their overall width is about
50%
of whatever parent their are a child of. This is normally not an issue, yet as soon as you start working on a given issue, update its state, attach a revision to it, then those custom fields become very small and difficult to read (especially in case of text-areas).It would be really nice, if the width could be expanded to
100%
of the parent container, whenever a tracker has history and or associated revisions.The text was updated successfully, but these errors were encountered: