[overlord-issues] [JBoss JIRA] (SRAMPUI-77) All Artifact Filters should be encoded in the URL

[Eric Wittmann (JIRA)]

    [ https://issues.jboss.org/browse/SRAMPUI-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12813894#comment-12813894 ] 

Eric Wittmann commented on SRAMPUI-77:
--------------------------------------

After discussing with the UX team, creating a new unique URL for every change made to the filters would result in too many items added to the browser history.  Instead, we decided to solve this issue by doing the following:

1) Remember the "last" value of the filter settings, so that when the user navigates back to the Artifacts page from the Artifact Details page (for example) we can show the old filter settings (note: this includes the page #)

2) Offer a "share this" feature on every page in the UI - this allows the user to bookmark the page.  Ideally the "share this" link generated by this feature will be to a permalink servlet which contains all of the query parameters needed by the page.  The permalink URL will not contain a # - the permalink servlet will process the URL and redirect the user to an "application" url that *does* include the #.  This also solves the problem of SSO redirects breaking application URLs.
                
> All Artifact Filters should be encoded in the URL
> -------------------------------------------------
>
>                 Key: SRAMPUI-77
>                 URL: https://issues.jboss.org/browse/SRAMPUI-77
>             Project: S-RAMP UI
>          Issue Type: Enhancement
>            Reporter: Eric Wittmann
>            Assignee: Eric Wittmann
>             Fix For: Future (Unscheduled)
>
>
> Whenever a filter is changed on the Artifacts page, it should be encoded into the URL.  This will allow users to bookmark actual queries.  It will also allow users to navigate back and forth without losing their place in the search.
> Note: also save the page # in the URL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira