Bug 7383 - Handle project not specified gracefully
Summary: Handle project not specified gracefully
Status: VERIFIED FIXED
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.9 M1
Assignee: Michael Wood
QA Contact: Alexandru Roman
URL:
Whiteboard: GUI design available
Depends on:
Blocks:
 
Reported: 2015-03-02 14:52 UTC by Michael Wood
Modified: 2015-09-01 11:51 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
select-project.png (29.77 KB, image/png)
2015-03-02 15:51 UTC, Belen Barros Pena
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Wood 2015-03-02 14:52:33 UTC
If a user goes to a page in toaster from their bookmarks or a link from memory, or in a new browser/different pc and if they haven't selected a project or got a current session toaster will just 500 out on them, we can fix this by sending them to the /projects page for instance.
Comment 1 Michael Wood 2015-03-02 15:48:02 UTC
(In reply to comment #0)
> If a user goes to a page in toaster from their bookmarks or a link from
> memory, or in a new browser/different pc and if they haven't selected a
> project or got a current session toaster will just 500 out on them, we can
> fix this by sending them to the /projects page for instance.

Though just testing that it seems a bit jarring as you have no idea why you've been dumped into the all projects page. So this need some design thoughts, over to you Belen!
Comment 2 Belen Barros Pena 2015-03-02 15:51:35 UTC
heh, I was about to submit this :)


    I think we should probably tell users what's going on. If we land them directly on the projects list without anything else, they will not understand why they are brought to a page that is not the one they wanted to go to in the first place.

    We could either:

    * Bring them to the all projects page with a notification on top

    * or we could use something like the landing_not_managed.html template, but with a different message (see attached image).

    But ideally, in both options, we would remember the page that was originally requested, and bring users directly there when they select a project.
Comment 3 Belen Barros Pena 2015-03-02 15:51:59 UTC
Created attachment 2427 [details]
select-project.png
Comment 4 Belen Barros Pena 2015-04-30 15:18:54 UTC
This is probably needed as part of the table refactoring effort that's currently ongoing. Assigning to Michael.
Comment 5 Michael Wood 2015-06-12 13:41:18 UTC
We now use a url schema that contains the current project identifier rather than having this value in the session.
Comment 6 Alexandru Roman 2015-09-01 11:51:18 UTC
verified on master: 71b0568fa43285f0946fae93fb43cea5f3bbecec