• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 1
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Description field location isn't respected in view screens, it's hardcoded in velocity templates JRA-5348

      JRA-27829 mentions that expand/collapse is stored in the users cookie, not saying it needs to be stored in database per user, just that an admin should be able to set a default (that gets overwritten if cookie exists).

      Filed against JIRA 6.2.6

            [JRASERVER-38722] Ability to collapse multi line custom fields by default

            I agree with the previous comment.

            fdo_orchestranetworks added a comment - I agree with the previous comment.

            Ideally, this would be on a per-field basis. For instance, I have several custom fields defined, some of which I know will be really long (such as a Stack Trace from a crash log), which I would want to have collapsed by default. But other multi-line fields might make sense to have expanded by default.

            Tim McDougall added a comment - Ideally, this would be on a per-field basis. For instance, I have several custom fields defined, some of which I know will be really long (such as a Stack Trace from a crash log), which I would want to have collapsed by default. But other multi-line fields might make sense to have expanded by default.

              Unassigned Unassigned
              3e81f6146e3f MC
              Votes:
              27 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: