• 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.

      As Crucible user I want to have a better universal inbox which lists all

      1. reviews I need to complete
      2. reviews I need to close
      3. comments I received an answer to (I haven't read yet)
      4. (unread) comments I was mentioned in using @mention functionality
      5. new unread comments (unread and read) in open or closed reviews I'm either author or reviewer.
      6. my non-closed code snippets

      so

      1. I don't miss anything in reviews
      2. I don't need to fallback to email notifications which partially duplicate what I already process in Crucible.
      3. No time is wasted on processing in both Crucible an Gmail.

       

      This can be called "Inbox" and replace existing "Inbox" you have in Crucible since existing is not practical due to the reasons highlighted.

      "Archive" action similar to Gmail should be present so if I'm fine with specific comment then I can archive (acknowledge) it. Read/unread is different flow - if comment is read it means I read it but have not yet processed/acknowledged. That's why you have "Archive" feature in e.g. Gmail.

      If at certain point the reviewer was removed from review then comments they added before should be in such "Inbox" unless they archived it. Currently if reviewer is removed from review then they can only access comments via email notifications or searching for such review in Crucible. But that's error-prone.

      PL-1339 is a similar story but was closed for some reason. See it for more details.

            [CRUC-7957] Crucible Inbox

            Atlassian Update – 31 January 2020

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 31 January 2020 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Kind regards Marek Parfianowicz Development Team Lead

            r added a comment - - edited

            I've took a liberty to put more detail into the description, opening as valid and reasonable new feature suggestion.

            I see you've added "(unread)" correction to the story description in few places. But it's not like we see it in order to make it effective. It does not matter if comment was read or not. I may often read comment or mark it as read. But it does not mean I fully acknowledged or processed it. Only comments that are processed should be removed from Inbox (CRUC-98).
            Similar workflow to what Gmail provides:

            Action Gmail Crucible with Comments Inbox (CRUC-7957)
            Marking read or unread Email thread can be read or unread Comment can be read or unread
            Archiving You archive (process, acknowledge etc.) thread so it's no longer seen is your inbox You archive (complete as per CRUC-98) comment so it's no longer seen in your inbox.

            r added a comment - - edited I've took a liberty to put more detail into the description, opening as valid and reasonable new feature suggestion. I see you've added "(unread)" correction to the story description in few places. But it's not like we see it in order to make it effective. It does not matter if comment was read or not. I may often read comment or mark it as read. But it does not mean I fully acknowledged or processed it. Only comments that are processed should be removed from Inbox ( CRUC-98 ). Similar workflow to what Gmail provides: Action Gmail Crucible with Comments Inbox ( CRUC-7957 ) Marking read or unread Email thread can be read or unread Comment can be read or unread Archiving You archive (process, acknowledge etc.) thread so it's no longer seen is your inbox You archive (complete as per  CRUC-98 ) comment so it's no longer seen in your inbox.

            I've took a liberty to put more detail into the description, opening as valid and reasonable new feature suggestion.

            Piotr Swiecicki added a comment - I've took a liberty to put more detail into the description, opening as valid and reasonable new feature suggestion.

              Unassigned Unassigned
              f8bd33572279 r
              Votes:
              9 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: