[JBoss JIRA] (SRAMPUI-96) Remember the selected filter criteria when navigating the UI
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMPUI-96?page=com.atlassian.jira.plugin... ]
Eric Wittmann updated SRAMPUI-96:
---------------------------------
Fix Version/s: 0.3.1
(was: Future (Unscheduled))
> Remember the selected filter criteria when navigating the UI
> ------------------------------------------------------------
>
> Key: SRAMPUI-96
> URL: https://issues.jboss.org/browse/SRAMPUI-96
> Project: S-RAMP UI
> Issue Type: Enhancement
> Components: View
> Affects Versions: 0.3.0
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1
>
>
> The Artifacts page allows the user to select a number of filters to narrow down the list of artifacts being viewed. However, these options are lost when the user navigates to another page and then back again. We should remember the user's filter settings as long as they stay within the s-ramp application (or perhaps beyond by storing something in browser state?).
--
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
11 years, 2 months
[JBoss JIRA] (SRAMPUI-77) All Artifact Filters should be encoded in the URL
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMPUI-77?page=com.atlassian.jira.plugin... ]
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
11 years, 2 months
[JBoss JIRA] (SRAMPUI-112) Properly handle logged-out errors
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMPUI-112:
-------------------------------------
Summary: Properly handle logged-out errors
Key: SRAMPUI-112
URL: https://issues.jboss.org/browse/SRAMPUI-112
Project: S-RAMP UI
Issue Type: Bug
Components: View
Affects Versions: 0.3.0
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.3.1
If the user has been logged out of the UI session (e.g. by explicitly logging out on another browser tab) then all sorts of things might break. Any of the RPC calls (errai) will likely fail. Additionally, the download and upload servlets will no longer work.
Need better handling of this situation.
--
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
11 years, 2 months