Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

Getting Started Integration : ngx-forge/ngx-launcher in Openshift.io #2178

Closed
invincibleJai opened this issue Feb 5, 2018 · 9 comments
Closed

Comments

@invincibleJai
Copy link
Collaborator

invincibleJai commented Feb 5, 2018

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

@rkratky
Copy link
Collaborator

rkratky commented Feb 27, 2018

@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.

@joshuawilson
Copy link
Member

if this is now an epic, please update the description to match

@invincibleJai
Copy link
Collaborator Author

Thanks @rkratky , have added it. Currently work is in progress , had synced up with @Preeticp as well. Will keep you updated.

@qodfathr
Copy link
Collaborator

qodfathr commented Mar 1, 2018

@joshuawilson what's an Epic? Haven't we moved on from those... :)

@joshuawilson
Copy link
Member

The devs are still using epic and user-story. As he called it a User-story but labeled it Epic.
Is it a bad thing to let them use those labels? You could double up the labels so it works for you too.

So this issue could have type/user-story and type/feature. Just need the parent.

@qodfathr
Copy link
Collaborator

qodfathr commented Mar 2, 2018

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.

@joshuawilson
Copy link
Member

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?

@invincibleJai
Copy link
Collaborator Author

invincibleJai commented Mar 8, 2018

Sure @joshuawilson will work through it.

As per my understanding, we wanted it as an epic which will have user-story associated with it.
I was not aware if we are not supposed to use Epic's

CC @arunkumars08 @jyasveer @sivaavkd

@invincibleJai
Copy link
Collaborator Author

@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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.