Bug 1020560

Summary: RFE: Do bug link validation before downloading all the topics
Product: [Community] PressGang CCMS Reporter: Lee Newson <lnewson>
Component: CSProcessorAssignee: Lee Newson <lnewson>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.2CC: mcaspers
Target Milestone: ---   
Target Release: 1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-03 22:16:38 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:

Description Lee Newson 2013-10-17 22:35:16 UTC
Bug links don't need the topics to be downloaded to be checked and as such it would be quicker if the check was done first. This means that users wouldn't have to wait for the topics to be completely downloaded (which can take quite a while for large books) just to find out their bug link values are incorrect.

Comment 1 Lee Newson 2013-11-06 02:18:51 UTC
Fixed in 1.3-SNAPSHOT build 201311061209

The processor will now do the validation in the following sequence:

Starting first validation pass...
Starting bug link validation pass...
Attempting to download all the latest topics...
Starting second validation pass...

instead of the old sequence:

Attempting to download all the latest topics...
Starting first validation pass...
Starting second validation pass...
Starting bug link validation pass...

Comment 3 Matthew Casperson 2013-11-24 21:38:43 UTC
Confirmed that bug link validation is now done as one of the first steps.

However, in testing this I noticed that "JIRAProject = Not a project" would validate without error, either in the server logs, through the web ui or in csprocessor.

Comment 4 Lee Newson 2013-11-24 22:57:13 UTC
Since that is another bug and nothing to do with this, I'm going to moved this to VERIFIED and create a new bug for that issue.

Comment 5 Lee Newson 2013-11-24 22:59:04 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=1033978 for that bug.