evolvewh

The task is CORE-2397 which appears to be a side affect of CORE-912

Go to the page(s) you want to quick link and you'll see a star on the left side of your screen just below the menu. Click it and it'll turn solid yellow meaning you've created a quick link.

Go to the page(s) you want to quick link and you'll see a star on the left side of your screen just below the menu. Click it and it'll turn solid yellow meaning you've created a quick link.

Are you saying that services ordered where a package is set to use pro rata to the 1st, generates the invoice correctly but the service renew date is not based on the pro rata date, but rather the anniversary date of the order?

Here's the latest response from internetbs:
 

Here's the latest response from internetbs:
 

No, requires change a entry in the modules table in the DB. We can migrate the module for you, only open a ticket in our client area and we will help you :).

Ok, so a couple points:
When a payment account is created, if it's the only one, set it as the default. When a payment account is created, and it's not the only one, ask if it should be the default?

I just took a few minutes to contact them (even though we don't use their service) and they're going to look into the issue(s). Hopefully they'll decide to make their own module to support Blesta and maintain it. Who knows but it's worth a shot to help @kikloo and others.

i prefer it also to be in the near future and why not in a beta of 4.1
i feel the tasks of  4.1 sprints has something left ?!
 

I just noticed that the add ons should have the same fix applied that CORE-2016 addressed.

This is one I want personally myself. It's tentatively assigned to 4.1, but is not assigned to any of the planned sprints. I bumped it to the top of the backlog, so we'll see. If not 4.1 (which is well underway), probably 4.2. I don't want to delay 4.1, but if there's time we'll have a look at it.

This will be a good one.

I don't know if this is a waste of time or not but it seems like the similar issue:
http://stackoverflow.com/questions/36087034/nvd3-chart-starts-out-squished-in-browser
 

I Can confirm this in FF windows 10. After a refresh page the graph are showed correctly .

I just thought I'd make a post here letting Blesta Devs know that the graphs and the home page and the billing overview screens still don't work 100%. I keep trying to find a pattern to how / when they happen. I was just on the support ticket screen and went to the dashboard and those graphs didn't load until I refreshed the screen again. I'm using v4.0.1

If you create a single feature request for 20 features it's pretty much guaranteed to be ignored. When we consider a request, and change it's status to "Planned", for example, it means we are planning to do what the task describes. If there are 20 things in the task, and we only plan to do 5 of them, well, you can see the problem.
Now, if the feature request is something like "Add an Affiliate System", we don't expect that to be broken down into every feature of the affiliate system in separate requests. That would be ridiculous. While there may be many parts to an affiliate system, it's a single new feature.
Making 20 changes to an existing feature isn't a single request, it's 20. And that's what we're talking about when we're talking about adding improvements to the Support Manager.
For example, this request - https://requests.blesta.com/topic/support-tickets-add-a-from-column-on-ticket-list-page is very specific, and concise, and it has already been scheduled for development. This is a good example of a feature request.
Thinking about it this way makes it easier for us to look at a request, approve it, create a task for it in Jira, and follow it through to completion.

Go to each package and the option is there to enable / disable

Awaiting staff or client reply is a good status and already requested but not yet implemented in the core.

I need to come back to this and document the code for anyone wanting to use this but I was able to modify the client area a bit for support tickets in v4.0

 
Version used: 4.0
Backup all Support Manager files and database first!!!
The following allows you to:
1) Add the status 'On Hold'
2) Add the different statuses in 'tabs' like you see above
3) Modify the status (mainly to change 'open' to Awaiting Staff or Client Reply')
What I did not do: I did not edit the 'tabs' on the client view page from the admin side; it's only edited under Support -->> Tickets on the admin and client side.
plugins/support_manager/views/default/admin_tickets.pdt
Line 8, add:
['name'=>$this->_('AdminTickets.index.category_on_hold', true) . ' <span>(' . $this->Html->_($status_count['on_hold'], true) . ')</span>', 'current'=>($this->Html->ifSet($status) == 'on_hold' ? true : false), 'attributes'=>['href'=>$this->base_uri . 'plugin/support_manager/admin_tickets/index/on_hold/', 'class'=>'ajax']],  
plugins/support_manager/language/en_us/admin_tickets.php
Line 28, add:
$lang['AdminTickets.index.category_on_hold'] = 'On Hold';  
plugins/support_manager/controllers/admin_tickets.php
Line 102, add:
'on_hold' => $this->SupportManagerTickets->getStatusCount('on_hold', $this->staff_id), Line 179, add:
'on_hold' => $this->SupportManagerTickets->getStatusCount('on_hold', $this->staff_id, $client->id),  
plugins/support_manager/views/default/client_tickets.pdt
Line 15 - 19 become:
          
 ['name'=>$this->_('ClientTickets.index.category_open', true) . ' <span>(' . $this->Html->_($status_count['open'], true) . ')</span>', 'current'=>($this->Html->ifSet($status) == 'open' ? true : false), 'attributes'=>['href'=>$this->base_uri . 'plugin/support_manager/client_tickets/index/open/', 'class'=>'ajax']],             ['name'=>$this->_('ClientTickets.index.category_awaiting_reply', true) . ' <span>(' . $this->Html->_($status_count['awaiting_reply'], true) . ')</span>', 'current'=>($this->Html->ifSet($status) == 'awaiting_reply' ? true : false), 'attributes'=>['href'=>$this->base_uri . 'plugin/support_manager/client_tickets/index/awaiting_reply/', 'class'=>'ajax']],             ['name'=>$this->_('ClientTickets.index.category_in_progress', true) . ' <span>(' . $this->Html->_($status_count['in_progress'], true) . ')</span>', 'current'=>($this->Html->ifSet($status) == 'in_progress' ? true : false), 'attributes'=>['href'=>$this->base_uri . 'plugin/support_manager/client_tickets/index/in_progress/', 'class'=>'ajax']],             ['name'=>$this->_('ClientTickets.index.category_on_hold', true) . ' <span>(' . $this->Html->_($status_count['on_hold'], true) . ')</span>', 'current'=>($this->Html->ifSet($status) == 'on_hold' ? true : false), 'attributes'=>['href'=>$this->base_uri . 'plugin/support_manager/client_tickets/index/on_hold/', 'class'=>'ajax']],             ['name'=>$this->_('ClientTickets.index.category_closed', true) . ' <span>(' . $this->Html->_($status_count['closed'], true) . ')</span>', 'current'=>($this->Html->ifSet($status) == 'closed' ? true : false), 'attributes'=>['href'=>$this->base_uri . 'plugin/support_manager/client_tickets/index/closed/', 'class'=>'ajax']]  
plugins/support_manager/language/en_us/client_tickets.php
Lines 19-22:
$lang['ClientTickets.index.category_open'] = 'Awaiting Company Reply'; // Modify this any way you want to display to your clients in their account area $lang['ClientTickets.index.category_awaiting_reply'] = 'Awaiting Client Reply'; // Modify this any way you want to display to your clients in their account area $lang['ClientTickets.index.category_in_progress'] = 'In Progress'; $lang['ClientTickets.index.category_on_hold'] = 'On Hold';  
plugins/support_manager/controllers/client_tickets.php
Line 81 - 85 become:
'open' => $this->SupportManagerTickets->getStatusCount('open', null, $this->client_id),             'awaiting_reply' => $this->SupportManagerTickets->getStatusCount('awaiting_reply', null, $this->client_id),             'in_progress' => $this->SupportManagerTickets->getStatusCount('in_progress', null, $this->client_id),             'on_hold' => $this->SupportManagerTickets->getStatusCount('on_hold', null, $this->client_id),             'closed' => $this->SupportManagerTickets->getStatusCount('closed', null, $this->client_id) plugins/support_manager/models/support_manager_tickets.php
Line 301, add:
where('support_tickets.status', '!=', 'on_hold')-> Line 1192, add:
'on_hold' => $this->_('SupportManagerTickets.status.on_hold'), Through phpMyAdmin, update the database to add 'on_hold'
Table: support_tickets
Go to structure and add 'on_hold' to the status column

Code has been added to the first post.

That's a lot smarter idea. Thanks!

Code has been added to the first post.

Code has been added to the first post.

you shouldn't do this , it will impact the whole tickets you have in the system .
a simple way without changing a lot of file is rename the department with a leading number as you want the order something like
04- Support
01- Sales
03- Billing
02- Domaines
then in the client_tickets.php in departments() function add the sort array before you set in in the view.
ksort($departements); i hope this will work for you .