#356 Blocker Proposal is Slow
Closed: Fixed None Opened 11 years ago by tflink.

= problem =

While the blocker proposal functionality does work, the process of actually proposing the blocker is very slow - it appears as if the page has just stalled for a while as the request is being submitted to bugzilla

Outside of being an annoyance, there is a possibility of users refreshing the page during submission, which would trigger a second proposal. This isn't the biggest issue ever but could end up generating extra comments in bugs.

= analysis =

It would be better to show users a "bug is proposing" page until the proposal is complete - that way they wouldn't be tempted to refresh the page and if the page is done correctly, it wouldn't matter if the page was refreshed or not.

= enhancement recommendation =

I have some ideas on how to go about fixing this but I need to explore the details before figuring out if any of them are even practical or how long the implementation would actually take.


I did some digging into this and I don't think it's practical to plan on this for Fedora 19. It would be great but the blocker tracking app wouldn't be the only Fedora-related app that has some slow postings and I think our resources could be better spent elsewhere for now.

Login to comment on this ticket.

Metadata