Bug 435092

Summary:	Bugzilla should automatically reload page after its modification -- processing (after adding a comment for example).
Product:	[Community] Bugzilla	Reporter:	Jan Lieskovsky <jlieskov>
Component:	Creating/Changing Bugs	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	devel	CC:	mcepl, sgreen
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-31 14:50:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Lieskovsky 2008-02-27 10:56:06 UTC

Description of problem:
Bugzilla doesn't automatically reloads page after its processing, 
so subsequent using "Copy Link Location" in FFX will result in
links like the following ones:

https://bugzilla.redhat.com/process_bug.cgi#c5

Instead of correct link to the comment of the bug:

https://bugzilla.redhat.com/show_bug.cgi?id=429692#c5

Version-Release number of selected component (if applicable):
devel

How reproducible:
Always

Steps to Reproduce:
1. Modify some bugzilla page (add comment || change the state of some bug)
2. process_bug.cgi script will appear to handle your form (correct)
3, Bugzilla doesn't do automatic reload (the main page is 
   still bugzilla.redhat.com/process_bug.cgi)
4, You need to click to link: "Changes submitted to bug: BZ#" to get
   to the original bug number page  

Actual results:
Bugzilla doesn't reload a page after processing it

Expected results:
Bugzilla should automatically reload script "process_bug.cgi" to
original bug number after 1-2 seconds to be able to use "Copy Link Location"
correctly (this is causing misunderstanding when you copy and paste
such links in subsequent email communication to point to some link..)

Additional info:

Comment 1 Matěj Cepl 2008-08-26 22:13:26 UTC

No need to reload the page -- a bit of Javascript could help. See http://mcepl.fedorapeople.org/scripts/greasemonkey/redhat/fixProcessLinks.user.js for inspiration.

Comment 2 Jeff Fearn 🐞 2012-05-30 04:45:50 UTC

As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.

If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.

Thanks, the Bugzilla team.

Comment 3 Jeff Fearn 🐞 2012-05-30 04:45:50 UTC

As part of the recent Bugzilla 4.2 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.

If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.

Thanks, the Bugzilla team.

Comment 4 Jan Lieskovsky 2012-05-30 08:16:51 UTC

Yes, this bug / feature is still present in current version of Bugzilla.

Though as Matej pointed out, JavaScript could help to overcome the current behaviour (commented as requested not to close this bug. But will let Bugzilla team to decide if to implement this would be a handy feature).

Thanks, Jan.

Comment 5 Simon Green 2012-05-31 14:42:34 UTC

Jan: What version of firefox are you using? When I am using Bugzilla 4.2 (Firefox 12), the URL changes to show_bug.cgi?id=XXX once I've made a change.

  -- simon

Comment 6 Jan Lieskovsky 2012-05-31 14:46:09 UTC

Firefox 12.0 too.

Comment 7 Jan Lieskovsky 2012-05-31 14:48:19 UTC

(In reply to comment #5)
> Jan: What version of firefox are you using? When I am using Bugzilla 4.2
> (Firefox 12), the URL changes to show_bug.cgi?id=XXX once I've made a change.

But you are correct. It's fixed already (now more closely checked the URL).
There is no process_bug.cgi anymore => this bug can be closed.

Sorry for the turmoil && Thanks, Jan.

> 
>   -- simon

Comment 8 Simon Green 2012-05-31 14:50:08 UTC

(In reply to comment #7)
> It's fixed already