Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Login behavior #33

Open
kkoch opened this issue Jul 22, 2016 · 4 comments
Open

Login behavior #33

kkoch opened this issue Jul 22, 2016 · 4 comments

Comments

@kkoch
Copy link

kkoch commented Jul 22, 2016

If user creates a map and then wants to save it, but they have not logged in or created a MyGLOS account, they then are taken back to the default catalog page. In other words, they have now lost the map they just were working on creating. Suggest expected behavior to be that they get put back exactly where they were. [I know this because for some reason myGLOS lost my account or I can't remember what I used originally so I created a new one. Put me back to start and I recreated my map. Then it didn't show me as logged in anymore so I had to log in and it put me back to start.]

@kknee kknee added the MyGLOS label Jul 25, 2016
@kkoch kkoch added the bug label Sep 20, 2016
@kknee kknee modified the milestone: Update User Management Nov 29, 2016
@kknee
Copy link

kknee commented May 5, 2017

@kkoch can you test this once the portal comes back up?

@kkoch
Copy link
Author

kkoch commented May 5, 2017

This still works as I originally reported. Added to map, decided to save collection, Login to MyGLOS, after logging in it takes me to catalog view. Go to map, and it is just the default map - my map view (potential future collection) I was building is no longer there.

(NOTE: I tested on DEV and it works the same way)

@kknee kknee added the InJira label Jun 16, 2017
@kknee
Copy link

kknee commented Jun 16, 2017

added a task for investigating to Jira - if this is high effort may have to wait for next year

@kkoch
Copy link
Author

kkoch commented Sep 5, 2017

FYI Another example of this behavior is when user adds a buoy to map then clicks on 'manage alerts'. If they aren't logged in, they get the error message that they must be logged in order to manage alerts. They login, but then are put to the catalog page and now have to re-do their search and buoy placement before they can set their alert.

@kknee kknee added this to To Do in Data Portal Jan 18, 2018
@kknee kknee moved this from To Do to Not Tasked in Data Portal Jan 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Data Portal
  
Not Tasked
Development

No branches or pull requests

2 participants