List view

• Retirement

  Retire the old dashboard, unify the code base, move everyone over to the new dashboard.

  Due by June 26, 2013

  •8/8 issues closed
  100% complete0 open8 closed

• Bug Bashing One

  Let's clean up and refactor. * Test coverage to 80% on models. * Polish the search until it shines * Better add/withdraw error handling when you do not have a bank account associated with your marketplace * Etc!

  No due date

  •13/13 issues closed
  100% complete0 open13 closed

• Egress

  Once this milestone is complete users of the dashboard will be able to export transaction and account data. This does not include securely vaulted data, rather general transaction or account information that is available via the API.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• Beyond Parity

  * Implement all the iframe pages natively and do away with the iframe code * Implement the new activity and orders pages

  Due by July 30, 2013

  •6/6 issues closed
  100% complete0 open6 closed

• Build a single new page

  Create a single page that replaces the functionality of an existing embedded iframe page from the old dashboard. Likely candidates are the marketplace settings page, the transaction detail page or the account detail page. Pre-requisites: * Working ember models * Completed mocked up page

  No due date

  •2/2 issues closed
  100% complete0 open2 closed

• Parity

  > The state or condition of being equal In essence, this milestone is complete when we achieve parity with the existing dashboard in a native manner. In order to not discard functionality from the existing dashboard we need to employ a three-pronged strategy: 1. Routing (#45) 2. Create a way to embed the existing functionality from the existing dashboard within the new dashboard in such as way that it can continue to be used. 3. Migrate across existing functionality into the new look and feel. The first step may be best achieved by using an iframe to embed the current dashboard minus the navigation chrome. The second step will require each page to be migrated from a mako template to a handlebars template and the relevant logic taken from the existing dashboard and converted.

  Due by June 5, 2013

  •32/32 issues closed
  100% complete0 open32 closed

• Static site

  This milestone is complete when we have a deployable site that has the basic look and feel as outlined in @dmdj03's styleguide. This includes: static HTML for pages templatized Less / CSS with variables that can be tweaked to change the look and feel of the site modals / buttons / other html widgets

  No due date

  •10/10 issues closed
  100% complete0 open10 closed

• Get this shit deployable!

  Get this project to the point where it can be deployed at https://dashboard.balancedpayments.com whenever a commit is made on the release branch provided linting and testing all passes.

  No due date

  •7/7 issues closed
  100% complete0 open7 closed