Jump to content

nsc

Members
  • Posts

    22
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by nsc

  1. According to the info here:

    https://docs.blesta.com/display/user/Order+System#OrderSystem-LinkingtoaSpecificProduct

     

    It is possible to make a link like that:

    /order/config/index/label/?group_id=1&pricing_id=5

     

    With general type of order form, it works fine.

    As I need to offer client a domain name too - I choose "Domain and other".

    Now either I have a link to exact product and it works as "General" type (no domain check window), or I can use link:

    /order/config/preconfig/label

    that does not have capability of pointing to the exact package or pricing.

     

    Is there a way to have both (domain check window and having a link to exact package)?

     

    p.s. passing domain variable in url address would be nice too

     

     

  2. As far as I understand the icon in first column of email template list is to identify which of these email templates are enabled and which are not.

     

    I disabled few of them, and result is in screenshot - nothing changed.

    post-119-0-64313400-1469098516_thumb.png

     
     
    edit:
    Ok I've found more related info:
    It seems like it's not checking the default language.
     
    I've other language installed, and that 'other language' is a default one.
    When I disable that template in 'default language', the template list doesn't change (template list is checking if the english version is enabled only).
     
    Maybe it's worth to do a global disable/enable checkbox for all the languages?
  3. Blesta seem to have a Custom Fields option, but I do not see a feature to add this field to an invoice.

    post-119-0-02926900-1469083834_thumb.png

    Full company details in our country consists from Company name, Company registration number, VAT number if exist and address.

    I've added Company Reg. No. as a customfield to a client, but it's not being added to a clients invoice.

  4. When new user does the registration, it has to fill in the contact info over and over again.

     

    First info is for a module in use (DirectAdmin module in my case), then he must fill the info for a blesta account info, and then he has to fill in the info for the order.

    The last one actually has a small dropdown menu, with just created user info, but I've noticed it only when I was half way done with filling all the info. It's a big chance the same may happen to a user in hurry too.

     

    May all the forms be autofilled with the info by default if the 'contact user' is already created? This would give less frustration with the whole registration and ordering process. If user needs to fill new contact info, he will just create a new user.

    Much bigger probability is that user will use the same account info over and over again, than a new one each time, so why not to fill that info by default and decrease the amount of clicks?

  5. I use only DirectAdmin module, so I'm not sure if the same thing is on other modules.

     

    When a new order is being created by a user, he must fill the username and password of the future DirectAdmin account. As this part doesn't do any checks - nobody knows if the account is going to be created successfully (an actual account creation happens only after invoice is paid). After these credentials, user has to fill the username and password again, this time for blesta account, but that's a different story.

     

    I'd suggest to implement ability to autogenerate username with some preffix + autoincrement, and autogenerate password for that new account, that user wouldn't even have to see that part in registration process (the less clicks for user, the bigger chances of getting a new customer).

     

  6. When new account is being created, and it fails for some reason (password doesn't meet requirements, domain already exists on server, username already exists on server, maybe a connection to directadmin server fails) - blesta give only that error happened. That's it.

     

    This makes blesta manager to test all the variations of possible causes or if that person have enough permissions - go to directadmin server to check the log.

    I'd say it would be much easier if blesta could output an error message that DirectAdmin API gives.

     

  7. It's not good to delete invoices just like that, as in our country the law also requires that all the invoice numbers would go sequentially. Deleting older invoice would give a missing invoice number. So plugin that deletes all the voided invoices is a "no go".

     

    Rather that, I'd suggest having ability to delete just the latest invoice. For example You created invoice for a wrong user or made some different kind of silly mistake. Maybe You tested something new. Deleting the latest invoice wouldn't be against a law, it doesn't break the numbering idea, it's wouldn't be related to any service yet, and You have ability to keep everything tidy.

  8. It's a popular payment gateway in Europe, that allows to collect payments, gives low rate transactions to the whole Europe.

    It can help collect payments from credit cards, even via banklinks in different countries.

     

    It already has ready to use plugins for systems as magento, exid eshop, zencart, whmcs and so on

    Most of the plugins are created for eshops, but there is also whmcs in the list:

    https://www.paysera.com/banklink_cms_plugins.html

     

    They provided development info on how the payments are made:

    https://developers.paysera.com/en/payments/current

     

    I don't know about the quantity of users that would love to have this, but I thought I add it to feature request. Maybe there will be more people that would be willing to see this payment gateway available.

  9. I've enabled DirectAdmin module in Blesta and added a DirectAdmin server.

    Then I tried to add service, and I got error about missing IP address, which was not present in a dropdown menu.

     

    The issue was only wrong credentials, but I didn't see that error anywhere, I just guessed the issue right.

     

    Showing error somewhere near the dropdown list would have helped me to solve the issue much faster. Also, DirectAdmin module could have a "test settings" button present. This would allow to make sure that everything is fine with connection and credentials itself.

     

    Other issue - when user is making order, he must fill the username and password for his new directadmin account.

    If the domain name or username is already present - the creation process fail without any error. May the DA error be shown in blesta in order to debug the issue faster?

     

    Also, autogenerating unique usernames and passwords and skipping that step in registration process would be even better (for example I could just specify some preffix in settings panel, and all the usernames would be incremented).

    With current order process user has to specify his new username and password 2 times. 

    After registration process if he presses to pay his invoice - new contact details form appears again... This page actually already has a small dropdown menu with just created user, but still, I didn't notice that menu at first and started filling the same info again(may that info just be autofilled by default with that newly created user?). That may happen to rushing clients too, and that refilling info over and over makes me 

     

    In order to have more successful orders and more clients, this part should go very smoothly and as less clicks as possible.

     

    Long story short (the #4 request idea came when I was writting about DA module, should I create a separate thread for it?):

    1. Show DirectAdmin error outputs.

    2. "test connection settings" in DirectAdmin module

    3. Autogenerate unique user and password invisibly when creating DirectAdmin account (may be autoincrement with a prefix).

    4. If user already filled his contact info - fill all the next forms automatically with the default user details, do not require to specifically select it.

  10. Is it possible to implement auto ticket status to "awaiting reply" when answering the ticket?

    Currently an extra click after each answered ticket is required to change status.

    Also if ticket is not assigned to anyone, after replying the ticket, it would be nice that it would be assigned to the person that answered it.

  11. Maybe the client could rely the information to the developer and developer's boss? Whose to say that the content of the ticket may not contain confidential information that the client doesn't wish to share with the developer? It could then be easy to accidentally send confidential information to third parties!

    We did that, but client wasn't very happy that he had to resend all the info each time.

    And when "client is always right", we don't have any other possibility, just to reply to all.

     

    No, I'm not kidding. It would be trivial to create an email that CC'd 10,000 people. Now you want Blesta to log all 10,000 CC addresses and email each one whenever the ticket is updated? That would clearly cause a denial of service that could effect not only your server, but also your mail service.

    Well, partially yes. But there could be a warning in RED or something similar that CC has more than 5 recipients.

    The warning could even be like "Suspicion of DOS: all CC were dropped"

     

    It's a security concern because it allows a multitude of users to reply to a single ticket. Blesta verifies the integrity of a ticket reply by evaluating the subject line. Allowing multiple people to reply to the same ticket can be a security concern as the reply is associated with the client and may not have necessarily come from the client.

    All replies may have an email on top or bottom that shows an email that it was received from. And if it's not the real client email, show it in red, maybe also add a warning. That's normal that other people adds some info to the same issue.

    To solve the problem of credentials being sent to the wrong address - email list could be added.

    I mean, there would be two possibilities "reply" and "reply to all". And near both of those buttons list of all receivers that would get that ticket answer. Usually "reply to all" doesn't have more than 3 receivers.

    Ability to remove mail addresses and add new ones to CC list would be uber-awesome.

    I'm not making feature request just to make unnecessary work for You guys. Every issue may have a solution. This feature would make support easier and more convenient, as currently it's impossible to reply to all, so I'm forced to reply via mail.

  12. What Denial Of Service ? People are having conversations all the time like that!

     

    What You suggest in situation when conversation is with client, his developer and developers boss?

    Just reply to the client that "our ticketing system developers says that CC will lead to dos, and we won't reply to all of You" ??? Are You kidding me???

     

    > "Moreover, you suggest anyone CC'd should be able to reply to the ticket. That's a security concern."

    That's not a security concern, it's people taking part in the problem solving.

     

    Ok, receiving separate mails is not end of the world, because blesta has the "merge" feature. But "reply to all" ???? How should I reply to all the people that have to be posted?

     

    Do You know that such "rules" of not making incredibly simple features does not let us to ditch simple mail?

    Every few tickets we have to reply via mail, because our ticketing system does not support simple "reply to all".

     

    p.s. kayako has this feature for ages. I haven't heard that it has any security issues with it

  13. No, One ticket - few receivers.

     

    Here is an example:

    I'm sending You mail about the problem + 5 people in CC, that have to know the wok flow of the problem solving.

    In this situation, You should reply to all, to keep all the people posted.

     

    But if You want to send a password to me in reply - You should send only to me and ignore all those 5 users in CC.

     

    Also all of the users in CC should have possibility to reply to the same thread (ticket).

  14. Hi,

     

    I have used few support systems, and I thought maybe to give blesta a shot, but there are small things missing, that would make live easier.

    I won't make separate tickets cause it simple requests, and don't want to make a lot of tickets.

     

    1. Adding + to one of existing requests: Custom ticket statuses with different colors in priorities (being able to change colors would be nice).

    So I'd love to have that feature also.

    Colors helps to notice more important tickets in a bunch of them. Custom statuses would help to personalize ticket system.

     

    2. Ability to quote messages, when doing reply. Having ability to choose quoting bellow answer or on top of my answer would be nice (i prefer quote bellow my answer).

    When client writes not one ticket, but few at once, quoting makes easier not to get lost for him between obtained answers.

     

    3. Ability to add signature per staff user.

    I think no need to explain why this is needed.

     

    4. Ability to change client in ticket.

    This is needed when You have some report, or problem in Your mail, but not in ticketing system. So You are able then just forward it to blesta, change ticket client to the real one, and give replies normally having all conversation with him. For example i have a cron that sends to blesta mails, that i sometimes need to write info to client, so creating new ticket and copy pasting all info to it takes unneeded time resources.

    Also might be that user went out for holidays or got fired, and that same job with all info should be done by having conversation with different person.

     

    5. Ability to forward ticket.

    When You need to get info from 3'rd party, it would be nice, that You could write to him from the same ticket, and when he would reply, it would be in one ticket, not in separate ones.

     

    6. Ability to add/remove columns in "Tickets" part.

    For example i would like to see client name and assigned stuff in there. Now I need to go to the exact ticket to see that information (yes, i know that it is written in "last reply" part when someone replies, but what if I replied those?)

    What if there are more than 20tickets at that time? view all of them ?

    I'm not a robot, i can't remember what status I saw some time ago, or what my colleague set in it by ticket numbers.

     

    7. Auto-action after reply?

    for example after answering tickets, it would be nice if it would go to "awaiting reply" or different status.

    Most of the time ticket has to go to the same status after reply, why it needs to be changed manually ?

     

    8. Auto-action after user reply?

    I answered to user, changed to "Awaiting reply" status, when user replied, it still was in "Awaiting reply".

    You should consider to add feature, automatically would change Status to for example "In progress" after user replies.

     

    9. Ability to merge tickets

     

    10. Ability to delete tickets

     

    ok, that's it for now.

    Would be nice to have information which features would have a shot in new version.

     

    nsc

×
×
  • Create New...