Description of problem:
When you create or edit Report Template, there is no Resource type in new input (inputs tab), when value type is selected to search. Resource type is shown only after user action, for example submit.
Version-Release number of selected component (if applicable):
This was found on sat 6.6 snap 7.
Steps to Reproduce:
1. Create or Edit Report Template
2. Open Inputs tab, click on Add input,
3. Change Value Type from Plain to Search
After value type is equal to Search, there is no line with Resource Type to choose.
When steps are done and user make an action (for example user submits Report Template), then resource type is visible.
Resource type should be visible immediately after value type is set to search.
Created redmine issue https://projects.theforeman.org/issues/27528 from this bug
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27528 has been resolved.
The previous problem seems to be solved, but there is another one unsolved problem, connected with this bug.
1. monitor -> report template -> create report template
2. inputs (tab) -> value type == Search
3. Add another input (button Add input) and there is automatically Value type Plain together with Resource Type - Activation Keys (which is wrong)
For Value type == Plain there should be field Options and not Resource Type.
Actual result: When user add another input, right after previous input where value type was equal to Search, then for Value type Plain there is still field Resource type.
Expected result: When user add another input, right after previous input where value type was equal to Search, then Value type Plain should display field with name Options instead of Resource type.
I hope it is okay to solve as one BZ instead of two.
did you mean to move the BZ to ASSIGNED/FailedQA? ON_DEV has a special meaning in Satellite6: https://ohsnap-satellite6.int.open.paas.redhat.com/docs/bugzilla
It would be ok by me, but upstream I will create separate bug and there is going to be another PR, maybe would be more readable to have another BZ as well.
Thank you Evgeni for link, yea I should use FailedQA. Yea you are right Ondrej, for better readability I just create separate bug - Bug 1743525.
As this is not a blocker bug for the next one, this is verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.