Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy new features to http://demo.riffplatform.com/ #247

Open
8 tasks
adonahue opened this issue Nov 14, 2019 · 2 comments
Open
8 tasks

Deploy new features to http://demo.riffplatform.com/ #247

adonahue opened this issue Nov 14, 2019 · 2 comments
Assignees

Comments

@adonahue
Copy link

adonahue commented Nov 14, 2019

As the CEO, I want our demo site to reflect all our new features, so that we are able to show and test the value of our product.

As a PM, I want users to create "regular" Riff accounts on our demo site, so that we do not need to maintain two sign-up processes (our and via Qualtrics), and so that users do not need to know the name of a document/room to use the demo site.

** Acceptance Criteria **
This story is to complete the following:

@adonahue adonahue added the sprint candidate Please review before Planning meeting label Nov 14, 2019
@adonahue
Copy link
Author

Per conversation w. @mlippert :

Probably missing step in here to create a new "prototype" branch from staging, into which the GT features above can get cherry-picked.

Also an open question about the timing for this story - should it be after the GT features are better vetted and deployed to GT staging.

@brecriffs
Copy link

It will be easier to estimate feasibility for the dashboard related items, once they are vetted. But this seems pretty easy, once we find a flow for organising prototypal work in a branch that we can cherrypick from.

@adonahue adonahue removed the sprint candidate Please review before Planning meeting label Nov 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants