Alternative to native support module in JIRA
In Alconost, we make videos about services and applications. For 4 years, we pereschupal hundreds of IT-products, among which there are interesting developments, worthy of a post on Habré. For example, recently we made a video about the HelpDesk for JIRA plugin for the company "Timlid".
What is interesting about this project? By the fact that it directly competes with the native support module for “Gira”, which, by the way, is in itself quite good, but expensive (for example, 5 users - $ 1500). It turns out that the plugin solves the same problem as the "parent" product, only cheaper.
By the way, here is the video we made:
')
A little more information about HelpDesk for JIRA - under the cut.
So, how much does HelpDesk for JIRA cost? For a team of up to 10 people - $ 10, regardless of the number of users who can send requests to the support.
For this amount, we get an adult functionality that allows you to build a complete user support system:
- client module: the client sees his requests and the status of their implementation;
- support module: it has options to “assign a task to such and such a contractor” and assessment of tasks by SLA;
- Executive module: everyone sees their tasks, their priority and, if available, customer comments and deadline.
It is the "consistency" of the functional that looks like the key feature of the plug-in (except for the price, of course). Each user ticket will go through all the cycles needed to solve the problem. The ticket will not be lost, the work on the bug will not be like a damaged phone, and the download of the performers and the movement for each ticket will be easily monitored.
It turns out that it is possible to organize work with user requests directly in JIRA, and at the same time it is not necessary to buy the native "Dzhirovsky" module at the price of a spare from Boeing. And it turns out that one should not be afraid of competition: the idea of ​​a product that does “the same thing, only cheaper” is quite viable.
And you know other examples, when a native solution can be painlessly and economically replaced by third-party ones? Or does a painless, at first glance, replacement always have a downside? Share your experiences in the comments!
about the author
Alconost is engaged in the localization of applications, games and websites in 60 languages. Language translators, linguistic testing, cloud platform with API, continuous localization, 24/7 project managers, any formats of string resources.
We also make advertising and training videos - for websites selling, image, advertising, training, teasers, expliners, trailers for Google Play and the App Store.
Read more: https://alconost.com
What is interesting about this project? By the fact that it directly competes with the native support module for “Gira”, which, by the way, is in itself quite good, but expensive (for example, 5 users - $ 1500). It turns out that the plugin solves the same problem as the "parent" product, only cheaper.
By the way, here is the video we made:
')
A little more information about HelpDesk for JIRA - under the cut.
So, how much does HelpDesk for JIRA cost? For a team of up to 10 people - $ 10, regardless of the number of users who can send requests to the support.
For this amount, we get an adult functionality that allows you to build a complete user support system:
- client module: the client sees his requests and the status of their implementation;
- support module: it has options to “assign a task to such and such a contractor” and assessment of tasks by SLA;
- Executive module: everyone sees their tasks, their priority and, if available, customer comments and deadline.
It is the "consistency" of the functional that looks like the key feature of the plug-in (except for the price, of course). Each user ticket will go through all the cycles needed to solve the problem. The ticket will not be lost, the work on the bug will not be like a damaged phone, and the download of the performers and the movement for each ticket will be easily monitored.
It turns out that it is possible to organize work with user requests directly in JIRA, and at the same time it is not necessary to buy the native "Dzhirovsky" module at the price of a spare from Boeing. And it turns out that one should not be afraid of competition: the idea of ​​a product that does “the same thing, only cheaper” is quite viable.
And you know other examples, when a native solution can be painlessly and economically replaced by third-party ones? Or does a painless, at first glance, replacement always have a downside? Share your experiences in the comments!
about the author
Alconost is engaged in the localization of applications, games and websites in 60 languages. Language translators, linguistic testing, cloud platform with API, continuous localization, 24/7 project managers, any formats of string resources.
We also make advertising and training videos - for websites selling, image, advertising, training, teasers, expliners, trailers for Google Play and the App Store.
Read more: https://alconost.com
Source: https://habr.com/ru/post/277665/
All Articles