2894: Archive reviews
- Fixed
- Review Board
| bert****@gmai***** (Google Code) (Is this you? Claim this profile.) | |
| May 2, 2015 | |
| 2955, 3014, 3562, 3645 |
What version are you running? 1.7.4 What's the URL of the page this enhancement relates to, if any? /dashboard/ Describe the enhancement and the motivation for it. A user should be able to archive a review. This would hide the review from the dashboard until there is further activity on it. There would be many benefits to this feature. 1) Keep the dashboard clean of reviews that don't require my attention. If I put in review comments, I don't want to see the review again until my comments are addressed. 2) Ignore irrelevant review requests. Especially with groups, you can get bombarded with review requests that you don't intend to take action on. 3) Hide old reviews. If reviews get tabled, sometimes indefinitely, they clutter up the dashboard until they are addressed months or sometimes even years later. Please provide any additional information below. See bug 1691 and bug 1453, comment 6 for more detail and previous discussions. Bug 1453 was closed suggesting that the "my comments" box fixes this, but I feel that's not a complete solution.
-
+ Component-Dashboard
What is the status of this? Is it being worked on?
Not actively. There are a ton of things to do and this isn't very high priority.
It's not (there's a lot of work on our plates right now), but we'd be happy to work with someone on a patch for this. Potentially a good student project, too.
-
+ StudentProject
Forgive me, but I see changes in 2.1 beta 1 like "Added the ability for extensions to provide new types of trophies," yet an important feature like this is not being worked on? My dashboard is a cluttered mess right now because of weeks-old and months-old reviews that I can't hide. How can I workaround this problem in the mean time?
We get a lot of contributions from students that we work with, especially trivial "starter projects" like that as they're learning the codebase. Difficult things like this aren't especially well suited for us to give to a student who's spending 8 hours a week for a single term. The 2.0.x releases have a feature that can automatically close review requests when code is pushed to the repository. I'd suggest working with your server admin to close out existing review requests that have been left open, and set up the commit hooks to turn on auto-closing. You can also bug your coworkers to clean up after themselves (they wouldn't leave a bug open after they had fixed it, I hope)
People leave finished reviews open all the time unfortunately, despite constant pestering. And really I shouldn't have to bug other people to get them to remove something that's on my own personal view. Fundamentally, I should be in charge of what I see on my dashboard, whether it's through filtering/tagging/archiving or some other capability. All other similar software I use works this way. I've been using RB since pre-1.0 and never understood why I can't do this. Anyway, I'll stop harping about this, but please reconsider the priority.
I think there's a lot of merit to a muting feature. It's just that there's a few hundred tasks that are all a high priority to somebody, and we're effectively only 2 full-time developers, so some things don't always make the cut. I'll give a bit of thought to how best to do this, and will see if it's doable as a student project, or if we can get a contributor to the project to look into it. Really, the best way to get such things into the product is to provide a patch, though, which I'd be glad to help provide guidance on.
-
+ Confirmed
I've just landed a bunch of archive/mute functionality on release-2.5.x, and more is coming. Enough is already in for me to call this "fixed"
-
- Confirmed + Fixed