-
Notifications
You must be signed in to change notification settings - Fork 66
Getting Started Integration : ngx-forge/ngx-launcher in Openshift.io #2178
Comments
@invincibleJai, could we please add the existence of respective docs to the acceptance criteria for this story? I filed fabric8io/fabric8-online-docs#192 to track the work on docs. |
if this is now an |
@joshuawilson what's an Epic? Haven't we moved on from those... :) |
The devs are still using So this issue could have |
This feels closer to an Experience (it's basically describing what the user would see/do in the acceptance criteria), but it would need a parent Scenario and child Features. |
This is a learning experience for everyone. As you are explaining it here. @invincibleJai can you work with @sivaavkd and @krishnapaparaju to update this according to what @qodfathr has said? |
Sure @joshuawilson will work through it. As per my understanding, we wanted it as an epic which will have user-story associated with it. |
@GeorgeActon let me if need to close it as we have planning done here #2440 and it has the list of user stories associated with it |
Description:
Currently, in OSIO we don't have mission flow. With this addition, it helps us to merge the flow from Launcher (i.e the mission, tech stack flow and others).
Acceptance Criteria:
OSIO user should be able to select mission, technology stacks than can proceed with Dependency Editor or move with selecting release strategy, Authorize Git Provider, Confirm Application Summary and creating a starter application. Associated Docs need to be there for this flow.
User Stories
[Sprint 145] - Getting Started - Services and Unit tests (User Story) #2274
[Backlog/would be Sprint 146] - Getting Started #2320
The text was updated successfully, but these errors were encountered: