Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-17213

Less comment nesting

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Having longer discussions in PRs is really a pain right now mostly because of nesting level. Every time one replies, it creates new nesting level. So having a discussion with a single person leads to very deep levels of nesting.
      One option right now to avoid it is to always reply to parent comment instead of comment one is replying to but that doesn't feel right.
      Instead would be nice if nesting would be create only if there is more than 1 reply to parent.

      For example

      • Comment 1
        • Comment 2 (Reply to comment 1)
          • Comment 3 (Reply to comment 2)
            • Comment 4 (Reply to comment 3)

      would turn to

      • Comment 1
        • Comment 2 (Reply to comment 1)
        • Comment 3 (Reply to comment 2)
        • Comment 4 (Reply to comment 3)

      If someone would make another reply to Comment 1, it would turn to this:

      • Comment 1
        • Comment 2 (Reply to comment 1)
          • Comment 3 (Reply to comment 2)
          • Comment 4 (Reply to comment 3)
        • Comment 5 (Reply to comment 1)

      Since "Comment 1" has 2 replies, "Comment 2" replies are nested and to indicate that it's part "Comment 2" thread, instead of being on same level as "Comment 5".

      Mind you that this does not imply any change in data structure and is purely UI optimisation for nested conversations.

      Attachments

        Activity

          People

            Unassigned Unassigned
            109bfee20b4f artursvonda
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: