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

Core Developer: Needs approval component #540

Open
1 task
ineedsubstance opened this issue Nov 10, 2016 · 0 comments
Open
1 task

Core Developer: Needs approval component #540

ineedsubstance opened this issue Nov 10, 2016 · 0 comments
Assignees

Comments

@ineedsubstance
Copy link
Contributor

ineedsubstance commented Nov 10, 2016

Design and build a component to show all content that needs approval in the approval workflow.

Feature: Access to content
  As a Core Developer,
  I want to provide the user with a list of content they created that needs approval
  So that they can keep track and take action on all their content that is in the approval workflow.

  Scenario: Needs approval
    Given that, a user is looking to see the content that they have submitted to the approval workflow
     When they visit the CMS home page
     Then they will see a list of they content they created that needs approval listed in chronological order
       And that list will display a maximum of 5 items
       And that list will include a link to view all items if there are more than 5
       And it will display the identifier
       And it will display the amount of time since the content has been sent for approval (ex. 5 days, 22 hours, 5 mins)
       And it will display the email address of the reviewer of that content
       And it will display a link that will allow users to edit the latest revision
       And it will display a link that will allow users to resend the request to the reviewer to review that content

Access to content:

  • Needs approval
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

1 participant