[forge-issues] [JBoss JIRA] (FORGE-589) Forge-generated searches should always allow for empty values in dropdowns

Marius Bogoevici (JIRA) jira-events at lists.jboss.org
Sun Jun 3 22:19:18 EDT 2012


     [ https://issues.jboss.org/browse/FORGE-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marius Bogoevici updated FORGE-589:
-----------------------------------

    Description: 
Can be currently observed at http://ticketmonster-jdf.rhcloud.com/faces/admin/event/search.xhtml

On search screens, Forge does not allow selecting an empty value on a dropdown if the target field is @NotNull ('Type' in this case).

This is wrong because:

a) Prevents users from searching 'all' types of entities (e.g. all kinds of events)
b) works incorrectly in conjunction with the initial page (which ignores the search criteria and retrieves 'all' events'). Assuming that FORGE-587 is worked around, after the initial page load, the 'Next' button will bring back all *Concerts* (4 items), which is not what the user actually expects (they expect the next 9 events instead)



  was:
Can be currently observed at http://ticketmonster-jdf.rhcloud.com/faces/admin/event/search.xhtml

On search screens, Forge does not allow selecting an empty value on a dropdown if the target field is @NotNull ('Type' in this case).

This is wrong because:

a) Prevents users from searching 'all' types of entities (e.g. all kinds of events)
b) works incorrectly in conjunction with the initial page (which ignores the search criteria and retrieves 'all' events'). Assuming that FORGE-587 is worked around, after the initial page load, the 'Next' button will bring back all *Concerts*, which is not what the user actually expects.




    
> Forge-generated searches should always allow for empty values in dropdowns 
> ---------------------------------------------------------------------------
>
>                 Key: FORGE-589
>                 URL: https://issues.jboss.org/browse/FORGE-589
>             Project: Forge
>          Issue Type: Bug
>          Components: Scaffold
>    Affects Versions: 1.0.5.Final
>            Reporter: Marius Bogoevici
>            Priority: Critical
>
> Can be currently observed at http://ticketmonster-jdf.rhcloud.com/faces/admin/event/search.xhtml
> On search screens, Forge does not allow selecting an empty value on a dropdown if the target field is @NotNull ('Type' in this case).
> This is wrong because:
> a) Prevents users from searching 'all' types of entities (e.g. all kinds of events)
> b) works incorrectly in conjunction with the initial page (which ignores the search criteria and retrieves 'all' events'). Assuming that FORGE-587 is worked around, after the initial page load, the 'Next' button will bring back all *Concerts* (4 items), which is not what the user actually expects (they expect the next 9 events instead)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the forge-issues mailing list