"Create a new project" action should consider the product from the URL

[vikasrohit]

Expected behavior

It should directly load the project details page for the specified product in URL.

Actual behavior

It loads Product selection screen instead.

Steps to reproduce the problem

• Open http://connect.topcoder-dev.com/new-project/wireframes.
• Enter few details e.g. name, ref code. Filling one should be enough.
• Now refresh the page.
• Click on "Create a new project" project button when asked for handling incomplete project
• Notice the page where it leads the user to

Screenshot/screencast

--

Environment

• OS: Any
• Browser (w/version): Any
• User role (client, copilot or manager): N/A
• Account used: N/A

[vikasrohit]

@fnisen should we load the wireframes details page or update the URL instead to not have 'wireframes'?

[fnisen]

@vikasrohit in this scenario, if they have the URL as http://connect.topcoder-dev.com/new-project/wireframes and they reload, I think we have to take them back to that page, not to the "You started a project with us recently" page. I think we just reload that page with their existing info, in case they reload accidentally, so nothing is lost.

This issue is related to what we were discussing here: #1035. I think changing the URL to mirror what is happening in the app would make the experience clearer for the user.

[vikasrohit]

@fnisen I guess we can not differentiate between user explicitly(or accidentally) reloading the page and reopening the tab/browser with this URL. So, IMO, I am afraid if we can avoid the "You started a project with us recently" page in such cases. If we do, it would not be loaded even when user is coming back to new project (may be by clicking the same marketing deep link after closing the tab/browser) later on.

Yes, it is related to #1035. I found this issue when working on #1035. 😬

[fnisen]

@vikasrohit sorry, I'm a little confused here. How do you want to proceed with this one?

[vikasrohit]

@vic-topcoder I think two tier menus, is good opportunity to handle this issue. I am thinking if we should directly show the project details form when user is coming back to the new project flow for the same project category and product i.e. if user has accessed /new-project/visual_design/wireframes previously and closed the tab and opens the same marketing link (/new-project/visual_design/wireframes) or refreshed the page somehow, we should take user to the project details form. However, if user clicks some different marketing link e.g. /new-project/visual_design/visual_design_concepts, we should show the incomplete project confirmation to user.

[vic-georgiev]

@vikasrohit let's not introduce the category as a part of the URL, this will create confusion in the future as categories can change, and projects in them also. It is much easier if the url is always following the <url>new-project/{project_short_name}

[vikasrohit]

@vic-topcoder Okay. Then we won't be able to track people who are leaving the project flow on project sub category selection screen as that screen would have same url as of select project category screen.

[vic-georgiev]

As per our last conversation: product categories can have their unique URL to allow tracking. ~/new-project/{project-category} and we'll keep all product URLs as ~/new-project/{project_short_name}. This allows each page to have a URL and fluidity in moving products between categories, which would preserve the URL for deep links (we share with external services and pages).

[vikasrohit]

It should be up there in dev.

[mtwomey]

Awesome, thanks, @vikasrohit. Victor confirms this is as desired in dev. Kindly deploy to prod.

[vikasrohit]

@mtwomey Okay. These changes would go to production only after full changes for two tier menu are tested in dev.

@vic-topcoder However, this issues is about having or not having category in the URL. The issue is described in the issue details and the solution is proposed in #1104 (comment) (ignore the project category in URL)

[vic-georgiev]

@vikasrohit what's the latest status of this one?