Open bdellasc opened 6 years ago
Adding some thoughts/expansions on what you have here:
I added the first bullet to my original list.
@Essjaysee RE: the OK behavior, @dlabrecq added functionality where the button will jump them back to a section that they haven't completed yet. We should look at it to see if it feels alright given that we want to encourage someone to "play" within this construct.
Addressed all but one issue in this story, and added some additional screens to the alt screens section in the InVision flow. Still need a bit more information on the Progress Screen based on the comments made in InVision a while back.
Added/reorganized this list since there are so many interconnected stories. I broke down sections of the launcher to a more granular level, since the stories we wrote for it have a copy and design component to them. This gap list is up-to-date as of 16 March 2018. @stacymcauliffe
Made a lot of progress updating the larger flow today - have not uploaded it to InVision yet.
Completed most of the edits. There are a few stragglers (around errors) that @stacymcauliffe is working through. I uploaded the entire experience to InVision
Added the specific open questions on the InVision Flow. All are awaiting Dev's reply.
Open Issues
Misc Issues
[ ] Resolve open questions to Dev (as of 2 April)
[ ] OSO Select Target Environment screen: Dev Comment: User needs to select a cluster they've provisioned. UX Question: Is this something they would do during the OAuth experience, or before that?
[ ] OSO Authorize Git Provider: Dev Comment: We didn't have an "Organization" dropdown for launch, but I guess we could add it. UX Question: Do you mean that you don't have that capability in the launch experience, or that you're expecting a "organization" dropdown here? If it is the later - organizations are shown in the location dropdown, along with user's repo area.
[ ] OSIO Import Create Application Screen: Dev Comment: underscores are invalid characters. UX Question: Are the requirements different between Launcher and OSIO for this?
[x] OSIO Import Summary Screen: Dev Comment: Do we need to check if any application with same name already exists? UX Question: In cases where they rename the application here, we'd probably need to run the same validation as the beginning of the flow. Can this be checked on that initial screen where the user names the application? Erik's answer: "there is a validation endpoint"
[x] OSIO Import Summary Screen: Dev Question: What are the default values provided for application name, maven artifact, group ID, version? Do we need validation on client side? Cat tagged Erik on the thread. Erik's answer: "these values used to come from the backend that is true, as they are just example values they could just as well be generated from the front-end values used where: groupId: io.openshift.booster artifactId: booster + missionId + runtimeId version: 1.0.0-SNAPSHOT and for node, we didn't display the groupId and made the version 1.0.0 and re-named the artifactId field "Name"
[ ] OSO/OSIO Navigate Away From Status Screen Mid-Process: Dev Comment: The way it has been build now closing the browser or navigation away will not stop the process it will only stop you from monitoring the progress UX Question: If the user navigates away and there is an error during the processes, can the user get back to this status screen to see what happened and remedy the problem? If they cannot, what kind of mess will they need to deal with if this happens?
[x] #888 Update mockups for Create space overlay
[x] #912 "Import application" flow gaps ???
Overall Consistency of Language/Voice in the Launch Experience
Update Launcher Experience InVision Mockups for Analytics Team reference
Closed Issues
1. Canceling out of experience:
2. Left bar behavior:
3. "Create Application Set Up" Progress Screen:
5. Other UI consistency issues