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

Manage plan status #87

Closed
stephaniesimms opened this issue Jan 9, 2017 · 4 comments
Closed

Manage plan status #87

stephaniesimms opened this issue Jan 9, 2017 · 4 comments

Comments

@stephaniesimms
Copy link

https://www.pivotaltracker.com/story/show/120867115

Plan statuses include:

  • draft

  • in review (call it something else; loose status w/no controls; add alerts for users to leave feedback on plans/notify when they receive new feedback)

  • complete

  • submitted: future status to mark plans of record/submitted to funder; corresponds with lifecycle; used for integrations, e.g., with repositories

Question about whether status changes can be done manually or whether they should only occur automatically (triggered by clicking a button e.g. "Export")

Note plan terms that correspond with the database:

  • Type (is it a test plan? y/n)
  • Status (draft...complete...)
  • Visibility (public/organizational/private)
@sjDCC
Copy link
Contributor

sjDCC commented Mar 1, 2017

Perhaps 'under comment' for 'in review' or do we need to differentiate this one?

@stephaniesimms
Copy link
Author

per discussions w/ @sjDCC and UX I think we just need an automatically triggered 'complete' status for MVP. this will help us manage the Public DMPs list (by only displaying 'complete' plans in the list #88) and potentially to manage the admin view into plans created by users at their org.

larger discussions about status/lifecycle should wait for maDMP future enhancements

@briri
Copy link
Contributor

briri commented Apr 12, 2018

We now have a complete flag in the database table @sjDCC and @stephaniesimms. This flag gets set when > 50% of the questions have been answered. Should this ticket be closed?

@stephaniesimms
Copy link
Author

yes let's close this stale issue. we have plan lifecycle/status indicators listed as a future enhancement on the wiki but it requires more discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants