905770 - Allow a refresh of bugs from the table

Status: NEW

(Webtools :: mediawiki-bugzilla, defect)

Description

[Brandon Savage [:brandon]]

Add a button/link that allows the cache to be cleared and the bugs to be refreshed in a table in mediawiki-bugzilla.

Comment 1

[Brandon Savage [:brandon]]

I created a pull request for this: https://github.com/mozilla/mediawiki-bugzilla/pull/39 If you can provide review that would be great!

Comment 2

[Lawrence Mandel [:lmandel] (use needinfo)]

Unfortunately, I've had no time to review recently due to my involvement in the Summit. The code change looks straightforward. Is there someone else who can provide this review?

Comment 3

[Lawrence Mandel [:lmandel] (use needinfo)]

Instead of adding a refresh option to every table in a page (many pages that make use of mediawiki-bugzilla include many tables) that refreshes the entire page, how about using a single button approach as we used with feature pages? For ex, see https://wiki.mozilla.org/Program_Management/Programs/Silent_Update#Features Will this approach work?

Comment 4

[Brandon Savage [:brandon]]

That's actually what this bug adds, at a table level.

Comment 5

[Lawrence Mandel [:lmandel] (use needinfo)]

(In reply to Brandon Savage [:brandon] from comment #4)
> That's actually what this bug adds, at a table level.

Right. My understanding is that it is not possible to refresh one table but that clicking refresh will actually reload the whole page. If that's the case, why not simply use a single button per page approach instead of having the option display multiple times on the page?

Comment 6

[Brandon Savage [:brandon]]

Once per page would assume that the objects know about each other when they don't. Also, people look at a table and go "hmm, this is wrong" and they don't want to look for a refresh button at page level, they want to see it locally. So it's a user experience thing. The user doesn't so much care about the mechanics as the action.

Comment 7

[Lawrence Mandel [:lmandel] (use needinfo)]

(In reply to Brandon Savage [:brandon] from comment #6)
> Once per page would assume that the objects know about each other when they
> don't. 

I'm not clear on the meaning of the objects knowing about each other. AFAIK, we can't refresh the data in one table without refreshing the entire page. As I understand it, clicking refresh simply sends a parameter that indicates that all of the data on the page should be refreshed. In this case the objects don't need to know about each other but simply that a refresh request has been made. Have I misunderstood something?

> Also, people look at a table and go "hmm, this is wrong" and they
> don't want to look for a refresh button at page level, they want to see it
> locally. So it's a user experience thing. The user doesn't so much care
> about the mechanics as the action.

I think this is a valid argument and I don't have any data to conclusively argue one refresh per page over multiple refreshes per page. My thinking is that, on wikimo, people are looking at data on a page level. As such, refreshing the entire page fits the conceptual model. As well, refresh per page is already familiar to people who have worked with feature pages, where this was the pattern.

Comment 8

[Brandon Savage [:brandon]]

There is a PR for this, waiting to be landed. I leave it to you.