Merge lp:~gmb/launchpad/add-next_check-to-bugwatch-pages-bug-558410 into lp:launchpad
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Graham Binns on 2010-04-09 | ||||
| Approved revision: | no longer in the source branch. | ||||
| Merged at revision: | not available | ||||
| Proposed branch: | lp:~gmb/launchpad/add-next_check-to-bugwatch-pages-bug-558410 | ||||
| Merge into: | lp:launchpad | ||||
| Diff against target: |
237 lines (+112/-20) 4 files modified
lib/lp/bugs/stories/bugtracker/xx-bugtracker.txt (+35/-12) lib/lp/bugs/stories/bugwatches/xx-edit-bugwatch.txt (+42/-1) lib/lp/bugs/templates/bugtracker-portlet-watches.pt (+14/-0) lib/lp/bugs/templates/bugwatch-portlet-details.pt (+21/-7) |
||||
| To merge this branch: | bzr merge lp:~gmb/launchpad/add-next_check-to-bugwatch-pages-bug-558410 | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Nelson (community) | ui | 2010-04-09 | Approve on 2010-04-09 |
| Abel Deuring (community) | code | 2010-04-09 | Approve on 2010-04-09 |
|
Review via email:
|
|||
Commit Message
Display the lastchecked and next_check values for BugWatches on the BugTracker overview and BugWatch +edit pages.
Description of the Change
This branch changes the BugTracker overview and BugWatch +edit pages so
that they now display a watch's next_check and lastchecked columns. This
will give users a better idea of when to expect a bug watch to be
updated.
== lib/lp/
- I've added tests to cover the new "Last checked" and "Next check"
columns.
== lib/lp/
- I've added tests to cover the new "Last checked" and "Scheduled"
items on the page.
== lib/lp/
- The lastchecked and next_check fields of each BugWatch are now
displayed in the BugWatch table.
== lib/lp/
- The lastchecked and next_check fields of each BugWatch are now
displayed on the +edit page.
| Graham Binns (gmb) wrote : | # |
On Fri, Apr 09, 2010 at 10:52:38AM -0000, Michael Nelson wrote:
> Review: Approve ui
> Looks great Graham. I noticed you are using approximatedate for the
> 'Last checked' column, which I think is correct, as seeing 3 days ago
> would be more helpful to me than 2010-04-06, but it seems that
> approximatedate only does so if the timedelta is <= 1 day... do you
> know why this is?
I don't know. Long forgotten design decision probably.
>
> Also why not simply use 'Last check' as the column heading? (ie. a
> noun, like 'Next check' and the other column headers).
No reason; I'll change it.
> Very insignificant thought regarding the ordering of the 2 col dls,
> would it be easier to scan if Created/Changed and Checked/Scheduled
> where vertically aligned like this:
True. I'll see if I can fix that in my next branch, which is going to
work on that page anyway.
> Tracker | Remote bug id
> Last status | Created
> Checked | Changed
> Scheduled | Created by
>
> Anyway, approved either way.
Thanks.
--
Graham Binns | PGP Key: EC66FA7D

Looks great Graham. I noticed you are using approximatedate for the 'Last checked' column, which I think is correct, as seeing 3 days ago would be more helpful to me than 2010-04-06, but it seems that approximatedate only does so if the timedelta is <= 1 day... do you know why this is?
Also why not simply use 'Last check' as the column heading? (ie. a noun, like 'Next check' and the other column headers).
Very insignificant thought regarding the ordering of the 2 col dls, would it be easier to scan if Created/Changed and Checked/Scheduled where vertically aligned like this:
Tracker | Remote bug id
Last status | Created
Checked | Changed
Scheduled | Created by
Anyway, approved either way.