-How bad is its impact? (Severity)
GUI is doing the correct thing. But with
GLASSFISH-15871 this is pretty confusing to user.
How often does it happen? (Frequency)
Whenever user wants to create a network listener, but also specify to create a new protocol that has already exist.
-How much effort is required to fix it? (Cost)
2 hours. The change of code is pretty trivial.
-What is the risk of fixing it? (Risk)
very small. Just add the test if network listener and protocol exist and inform user in that order. Instead of depending on backend.
-Does a work around for the issue exist? Can the workaround be reasonably employed by the end user?
Doesn't need any work around, whatever GUI doing now is technically correct.
If the issue is not fixed should the issue and its workaround (if applicable) be described in the Release Notes?
How long has the bug existed in the product?
Probably since the beginning.
Do regression tests exist for this issue?
There are some devtest for realm, will need to add more for this case.
Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
The usual test they run and the GUI dev test.
When will a tested fix be ready for integration?
Ready now, svn diff attached.