• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • We collect Confluence 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.

      Hello,

      We would like an improvement done to the table or table-plus macro(s) to have the ability to collapse/expand a row in a table.

            [CONFSERVER-20098] Ability to collapse/expand a row in a table

            Please re-open and review this feature

            Thanh (Tan) Nguyen added a comment - Please re-open and review this feature
            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3577028 ] New: JAC Suggestion Workflow 3 [ 4339088 ]

            i need to be able to expand / collapse rows in a table - aggregated under each header. Assume you have multiple phases and you need to expand or collapse milestones for each. Can any updates be provided on this - we all have been waiting for the for over 10 years

            Helen Ioffe added a comment - i need to be able to expand / collapse rows in a table - aggregated under each header. Assume you have multiple phases and you need to expand or collapse milestones for each. Can any updates be provided on this - we all have been waiting for the for over 10 years

            Not saying this isn't still a needed or nice to have feature, but I was able to insert an "expand" in my table row, so the contents of that cell can be expanded / collapsed.  That perfectly solved my use case.

            code faster added a comment - Not saying this isn't still a needed or nice to have feature, but I was able to insert an "expand" in my table row, so the contents of that cell can be expanded / collapsed.  That perfectly solved my use case.

            Eli Pielet added a comment -

            agree, this would be a very useful feature.

            Eli Pielet added a comment - agree, this would be a very useful feature.

            Wanna vote +1 for this, but can't.

            Andrey Dzhaksumbaev added a comment - Wanna vote +1 for this, but can't.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3169954 ] New: JAC Suggestion Workflow 4 [ 3577028 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3039851 ] New: JAC Suggestion Workflow 2 [ 3169954 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2524440 ] New: JAC Suggestion Workflow [ 3039851 ]

            Yes, please re-open this ticket! Maybe it was "won't fix" in 2011 but priorities should be reviewed.

            Here's our specific use case: we track milestones & status in a table, with 1 row for each relevant time period. When that's active, it's useful to have multiple bullet points or even short paragraphs. But once it passes into history, we'd like to collapse it. So, the info is still available, but not taking up much space. As is, we have to scroll down past old details in order to see what's current.

            Scott Lawton added a comment - Yes, please re-open this ticket! Maybe it was "won't fix" in 2011 but priorities should be reviewed. Here's our specific use case: we track milestones & status in a table, with 1 row for each relevant time period. When that's active, it's useful to have multiple bullet points or even short paragraphs. But once it passes into history, we'd like to collapse it. So, the info is still available, but not taking up much space. As is, we have to scroll down past old details in order to see what's current.

              smansour Sherif Mansour
              fff62676-2079-4236-bb5b-9ea4aae3f227 Deleted Account (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: