-
Suggestion
-
Resolution: Unresolved
As Crucible user I want to have a better universal inbox which lists all
- reviews I need to complete
- reviews I need to close
- comments I received an answer to (I haven't read yet)
- (unread) comments I was mentioned in using @mention functionality
- new unread comments (unread and read) in open or closed reviews I'm either author or reviewer.
- my non-closed code snippets
so
- I don't miss anything in reviews
- I don't need to fallback to email notifications which partially duplicate what I already process in Crucible.
- 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.
- relates to
-
BSERV-9034 [feature request] inbox message for comment in code review
- Gathering Interest
- supersedes
-
CRUC-6526 Reviews with new comments should be displayed in Inbox
- Not Being Considered
- links to
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