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

Admin UI changes #296

Open
gautamrege opened this issue Jun 30, 2017 · 1 comment
Open

Admin UI changes #296

gautamrege opened this issue Jun 30, 2017 · 1 comment
Assignees

Comments

@gautamrege
Copy link
Member

Here are some changes I need for admin access:

  • In Redemptions tab, we need to see the sum of all of Redemption Requests. i.e. 800$ or 1400$ etc.
  • Need a filter in Redemptions tab for Open/Closed redemptions.
  • Sorting on Columns (currently it's by date) but it's helpful to also be able to sort by Store. I can find out how many Amazon eGift cards I need to purchase!
  • Export Redemption Requests to CSV file.

Personal Profile: Everyone should be able to see the "points history" tab for all users. This will help motivate people.

sethu pushed a commit that referenced this issue Jul 12, 2017
* Sum of all of Redemption Requests[#296]

A helper method added to print the total capital value of redeemable
points.

* Sum of all Redemption Requests [#296]

A helper method added to display the capital value of total redeemable points.
prasadsurase added a commit that referenced this issue Jul 25, 2017
@amitk
Copy link
Contributor

amitk commented Jul 25, 2017

@gautamrege currently the third specification of sorting on columns is by store which is static
i.e

  • The records will be retrieved from the data base in sorted order on the basis of store then on
    by date.
    what sethu sir told me to implement is to load the table using StreamTable but the conflict is
  • StreamTable retrieves all records from db and perform pagination and sorting on columns on the client side.
  • The page is currently implemented using kaminari gem which performs pagination on server side.
    So, how we have to implement this specification.

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