Merge lp:~gmb/launchpad/add-next_check-to-bugwatch-pages-bug-558410 into lp:launchpad
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Graham Binns | ||||
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 | Approve | |
Abel Deuring (community) | code | Approve | |
Review via email: mp+23080@code.launchpad.net |
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.
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.