Bug 1658717

Summary: Agile Docs links incorrect
Product: [Community] Bugzilla Reporter: Ernesto Puerta <epuertat>
Component: DocumentationAssignee: Jeff Fearn 🐞 <jfearn>
Status: CLOSED CURRENTRELEASE QA Contact: Rony Gong 🔥 <qgong>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0CC: khong, qgong, sanjay.ankur
Target Milestone: 5.0-RH2   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.0.4.rh13 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 02:13:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ernesto Puerta 2018-12-12 17:54:24 UTC 
Document URL: 
https://bugzilla.redhat.com/page.cgi?id=fields.html#agile_pool.name points to broken/404 link (https://bugzilla.redhat.com/docs/en/html/extensions/AgileTools/index-user.html)

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:
Comment 1 Jeff Fearn 🐞 2018-12-12 22:55:10 UTC 
bah, the docs link on all the agile pages is similarly incorrect.

The correct URL is https://bugzilla.redhat.com/docs/en/html/integrating/api/Bugzilla/Extension/AgileTools.html
Comment 2 Jeff Fearn 🐞 2018-12-20 00:46:18 UTC 
Seems to have already been fixed in devel.
Comment 3 Rony Gong 🔥 2019-01-10 07:31:44 UTC 
Verified on commit: f6835a7f9
PASS
Comment 4 Jeff Fearn 🐞 2019-01-13 23:48:07 UTC 
*** Bug 1664765 has been marked as a duplicate of this bug. ***
Comment 5 Jeff Fearn 🐞 2019-02-06 07:11:02 UTC 
This change has been deployed to partner Bugzilla [1] for pre-release testing, if your testing reveals any issues please update this bug.

1: https://partner-bugzilla.redhat.com/
Comment 6 Jeff Fearn 🐞 2019-02-13 02:13:06 UTC 
This change is now live. If there are any issues, do not reopen this bug.                                                                                                           
Instead, you should create a new bug and reference this bug.