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

Purchases: Site order #165

Closed
scruffian opened this issue Nov 19, 2015 · 5 comments
Closed

Purchases: Site order #165

scruffian opened this issue Nov 19, 2015 · 5 comments
Assignees
Labels
[Feature] Purchase Management Related to managing purchases such as subscriptions, plans, history, auto-renew, cancellation, etc. [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it

Comments

@scruffian
Copy link
Member

The order of the sites in /purchases is currently based on the purchase date of their respective purchases. It should use the same order as the site picker.

@scruffian scruffian added [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it Upgrades labels Nov 19, 2015
@scruffian scruffian added this to the Purchases: View milestone Nov 19, 2015
@p3ob7o
Copy link
Member

p3ob7o commented Nov 19, 2015

I agree, with a little tweak: any site with a subscription in a special state (failed auto renewal, has expired, domain in grace period or redempion) should be pushed to the top.

@apeatling
Copy link
Member

+1

@fabianapsimoes fabianapsimoes modified the milestones: Purchases: v2, Purchases: v1 Nov 19, 2015
@fabianapsimoes fabianapsimoes added [Feature] Purchase Management Related to managing purchases such as subscriptions, plans, history, auto-renew, cancellation, etc. and removed [Feature] Purchase Management Related to managing purchases such as subscriptions, plans, history, auto-renew, cancellation, etc. Upgrades labels Nov 20, 2015
@fabianapsimoes fabianapsimoes modified the milestones: Purchases: v1, Purchases: v2 Nov 25, 2015
@stephanethomas
Copy link
Contributor

I agree, with a little tweak: any site with a subscription in a special state (failed auto renewal, has expired, domain in grace period or redempion) should be pushed to the top.

I'm not sure about that one because it means that the order is no more consistent with the site picker but also with what users are used to on this Purchases page - and when it's not predictable it forces users to think about the interface and it makes it feel less efficient. Moreover the majority of users only have one blog, only a few have twos, and as such they should be able to see that something requires their attention easily since the page wouldn't be that long.

@scruffian
Copy link
Member Author

I think that moving the site to the top if it is in a special case is probably a different issue, and probably needs some design thought - we might like to change the way it looks slightly to show that it's been bumped to the top for a reason.

We can easily handle these in two different PRs.

@drewblaisdell
Copy link
Contributor

I opened an issue for bumping purchases in certain states to the top of the list: #4620

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Purchase Management Related to managing purchases such as subscriptions, plans, history, auto-renew, cancellation, etc. [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it
Projects
None yet
Development

No branches or pull requests

6 participants