Switch to reviewboard-dev is good idea. Please describe there what You
expect.

On Apr 10, 10:10 am, Christian Hammond <chip...@chipx86.com> wrote:
> I wouldn't be opposed to such a view, but would like to see some design
> discussion on it first. I'm not sure if making a new view alongside
> Incoming/Outgoing/etc. is what we want to do.
>
> It might make more sense to have the ability to filter the dashboard, which
> could allow not only for showing only new unread review requests but also in
> the future we could expand on this. For example, making "To Me" a filterable
> thing so it could be applied to any view you're currently looking at.
>
> This might be better discussed on reviewboard-dev, but if you want to work
> on something, we could certainly figure out a design.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
> On Sat, Apr 10, 2010 at 12:57 AM, Jan Koprowski 
> <jan.koprow...@gmail.com>wrote:
>
> > 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-updatesview / link
> > for dashboard. This should be hard. May I?
>
> > Greetings from Poland!
> > --
> > Jan Koprowski!
>
> > On Apr 10, 9:12 am, Christian Hammond <chip...@chipx86.com> wrote:
> > > Hi,
>
> > > 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
> > > something.
>
> > > 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
>
> > > --
> > > 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 <jan.koprow...@gmail.com
> > >wrote:
>
> > > > 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
> > > >http://www.reviewboard.org/donate/
> > > > 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>
> > <reviewboard%2bunsubscr...@googlegroups.com<reviewboard%252bunsubscr...@googlegroups.com>
>
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/reviewboard?hl=en
>
> > > > To unsubscribe, reply using "remove me" as the subject.
>
> > --
> > Want to help the Review Board project? Donate today at
> >http://www.reviewboard.org/donate/
> > 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
> >http://groups.google.com/group/reviewboard?hl=en

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to