Description of problem:
If you create a case for Application Platform (EAP), in the version pick list you will see 4.3.0.GA, 4.2.0.GA, and 4.2.0.CP1. If you go over to Software Downloads and select Application Platform, in the version pick list, you will find a much longer list of version numbers from which to choose.

The reason for this discrepancy is because on the support side, the versions table is looked at to determine the possible versions. The versions table is also used by Issue Tracker. On the software downloads side, version numbers come from the software table.

This is problematic on a number of levels. Consider this scenario. A customer downloads bits for EAP 4.3.0.GA_CP03. The customer then wants to open a ticket against that product. He does not see 4.3.0.GA_CP03 in the case creation screen. The customer might choose to open a separate ticket complaining that the right version is not there. Or the customer may elect to choose a different. Either way, this could potentially lead to lots of confusion and a lot of extra work.

I think that the best solution is to use the versions table across the board. This will impact CSP and SEP, and possibly Issue Tracker.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
This problem is really symptomatic of a larger issue in which CSP is using to different data models (i.e., schemas) for support and for downloads. For support the tables that are used by Issue Tracker are used. Downloads relies on different tables. This creates a number of problems on a number of levels.