Leaderboard

This belongs to CORE-547 and is tentatively scheduled for 3.2. It's not complete yet, and is not guaranteed to be in this release.. but because it's client related, and the theme for 3.2 is "client area" I'd like to see it.

Yeah, we finally got our project management system public so people can follow progress, view the roadmap. By default, all items are private, and we've been slowly opening them up as we work on them. Will probably make an official announcement next week, sort of rolled it out silently.

Hello, Wen we have a signature, and open a ticket, wen we select an Predefined Response, it posts after the signature, and not before the signature. Regards, Paulo Vidal

I've added this to CORE-1055, tentatively set for 3.2

Unfortuneately, recurring payments are a bit more complicated for non-merchant gateways. Besides that Omnipay hasn't implemented recurring payments for GoCardless, there are some more fundamental problems with using recurring payments for hosting purposes in general. With many gateways if you setup yearly recurring payments it will do exactly that: charge today and attempt to charge exactly a year from now. However if you are for example selling domain names it would be nice to charge today and a number of days earlier next year. So that if the next payment for whatever reason fails, you can still work out an alternative payment method with the client, without the risk of the domain expiring, or the risk of you paying renewal fees out of your own pocket for a domain the customer may or may not end up paying.

It's tentatively assigned to version 3.2, but it's not complete. This is one of those we hope to get into the next release, but it all depends on how quickly we can wrap up the must haves. It may be bumped to 3.3.

While it may not be specifically a built in feature I really see that as a bug.

I'm not sure if that's a bug or a feature request mate but yeah it would help haha.