You are first.
I'am just found new updates column and want to ask is I may make
http://reviews.reviewboard.org/dashboard/?view=new-updates view / link
for dashboard. This should be hard. May I?
Greetings from Poland!
On Apr 10, 9:12 am, Christian Hammond <chip...@chipx86.com> wrote:
> Discard should only be used when that particular change has been abandoned.
> For example, if it's been decided that the feature or fix isn't needed, or
> There's no way to "clear" the dashboard like this. The dashboard isn't
> really intended to be like gmail or anything, where the person viewing it
> has full control of what's on there.
> The best solution I can give right now is to use the "My Comments" and "New
> Updates" columns to better see which review requests you've commented on and
> which ones have changed since you last looked at it.
> Perhaps down the road the dashboard can be modified to be more configurable
> and allow you to hide review requests until there's a new update. That's a
> lot of work and won't be happening in the near future, though.
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
> On Sat, Apr 10, 2010 at 12:04 AM, Jan Koprowski
> > Hi!
> > Is There a need to provide "mark as read" in ReviewBoard?
> > Reviewer from my company use ReviewBoard and they are very impressed
> > how easy and nice ReviewBoard is. He like dashboard. He asked me
> > something and I don't know how answer him.
> > He always want to have clear dashboard when him work is done. Only
> > way to do this is submit review when all is ok, or discard them when
> > something is wrong. But my feeling about discarding when 99% is ok but
> > only one line should be fixed is ... mixed. Is this a proper way? How
> > this will looks like.
> > When developer want to make review they run post-review.
> > Reviewer read all changes, comment and find one small tiny
> > insignificant detail which should be change. Because they want to
> > "mark" this review request "as read" they discard it to make it
> > disappear from the dashboard. When the dashboard is clear they now
> > they can start do other things.
> > When developer fix this tiny insignificant detail run post-review with
> > --reopen (in progress) and --review-request-id and resurrect review
> > request. And so on.
> > Is this good way? Or there is a "missing element" and "mark as read"
> > or "done for me" quasi-state should be provided?
> > Greetings from Poland!
> > --
> > Jan Koprowski
> > --
> > Want to help the Review Board project? Donate today at
> > Happy user? Let us know athttp://www.reviewboard.org/users/
> > -~----------~----~----~----~------~----~------~--~---
> > To unsubscribe from this group, send email to
> > reviewboard+unsubscr...@googlegroups.com<reviewboard%2bunsubscr...@googlegroups.com>
> > For more options, visit this group at
> > To unsubscribe, reply using "remove me" as the subject.
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at