Warning! You are viewing the old version of site.

You will be redirected to the new site in 5 seconds

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

What is CRM for JIRA?

CRM for JIRA provides a great opportunity to track companies, contacts, goods, etc. You should use these records within JIRA issues.

If you track support issues in JIRA, you could get a statistic through companies or contacts. Although, you can manage SLA's by your clients.

If you manage projects or sales in JIRA, you could get the information about sales by current client or his project history.

And now you can enable a special security level "Reporter's Colleagues", so all people from Reporter's Company will have got access to the issues.

 

Dictionaries in JIRA

You can track all your clients and contacts in JIRA now. Although, there are next dictionaries: Products, SLA's and Custom Dictionaries. The last one provides a simple track your own records such as: hardware, types of companies, people titles or something like that.

All dictionaries could be defined for your specific requirements. For example, you can add new attributes for company and define look and feel of record cards.

There is a spacial engine which is blocking record duplicates in the dictionaries. This means, when you try to add a new record, the CRM will tell you: "Hey guy, be careful! There are similar records here... look at these."

To find a record you should just start writing. It is simple, like a google search. If you want find records by several conditions you can use attributive search. It doesn't mean how many records do you have, hundreds or thousands. Just start looking..

SLA Management

If you want to do the best support in the word, you should manage and control issue reaction time. There is a powerful SLA custom field where you could define your own rules, time intervals, color schemes of priorities and work time calendars.

But SLA couldn't be linked with a company or contact SLA. You can use common JQL-queries to determine rules. For example, you can set up reaction time depends on issue type or project or something else.

You can control SLA violations by special report on the dashboard. Here you can find who is the most bad or well Assignee.

Security Level by Company

Если вы планируете обрабатывать обращения от разных компаний, то рано или поздно встанет вопрос о разделении прав доступа между пользователями. Наш плагин позволяет организовать сценарий предоставления прав доступа только сотрудникам организации автора обращения.

"Коллеги автора" хранятся в карточке организции, и при изменении этого списка автоматически поменяется список доступа к уже существующим в системе задачам. Это значит, что при увольнении сотрудника из организации, он сразу потеряет доступ к задачам.

Customer Satisfaction

Если вы хотите делать лучший саппорт в мире - делайте его вместе с клиентами. С помощью нашего плагина вы можете научить JIRA рассылать после решения запроса анкету для получения от автора обратной связи.

Оценки и комментарии, полученные от автора обращения, сохраняются в задаче и могут быть проанализированы позже.

Для интерактивного мониторинга удовлетворённости ваших клиентов можно вывести на рабочий стол специальный портлет, показывающий метрики удовлетворенности (Customer Satisfaction и Net Promoter Score) по направлениям вашей деятельности.


Marketplace Page | Documentation | Live Demo | Support

  • No labels