Will you develop a light-weighted support system (not JIRA), like BitBucket is for Git?

We have tested JIRA, ZenDesk, Desk, Kayako and even Redmine - and none really gave us what we needed, a flexible yet extremely easy-to-use support system - handling hundreds of support tasks every day by a handful of experienced support staff.

Does Atlassian plan to develop and release a "JIRA Support system" any time soon? JIRA is to extensive, with dozens of fields here and there, and - well, its too complicated for agile support staff as JIRA is more directed towards development issues.

3 answers

1 accepted

1 votes

We've made Jira work very well as a "light" support system - it's just a case of configuring it to only use the fields you need in a support environment in the support projects.

Have a look at https://confluence.atlassian.com/display/JIRA/JIRA+as+a+Support+System and https://confluence.atlassian.com/display/JIRAKB/Using+JIRA+for+Helpdesk+or+Support

Using it for support alongside development has some significant benefits - developers able to get involved in support in the same system they're using for development, users able to see development activity, support staff being able to reference support, development and project information in the same place. And so on.

Nic,


Thank for your details, although those articles are decades old so to say :)

We'll give it another run.

Very true, although they are maintained and still pretty valid.

Renjith Pillai Community Champion Dec 25, 2012

1. Not with plain JIRA. This should help - https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui

2. There are some workarounds by having 'if' conditions in the velocity templates at https://jira.atlassian.com/browse/JRA-161

Also this plugin claims to have email templates - https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.jjupin

Thanks for the extensive replies. We are not there where we want to spend time adding if's and such (we just want a system we can easily configure and get started with) and so, after heavily testing the last couple of days we have decided to keep on to Kayako for a little longer and see how JIRA evolves in terms of the above "issues".

Ok, two remaining issues before we are able to select JIRA as our support system;

1 - User count. We want each user to get a user account created when sending in issues, so that they can watch the issue status when logged in to JIRA. All technical details are set, however the license cost per user would kill us. Are there any way to not let certain customers be counted on the license plate?

2 - Emails. Email notifications are needed in lots of ways, however the email templating system doesnt seem well prepared for easy customization across projects and such - and having to modify "core" template files in a rather complex system is difficult. Are there any solution for easier email template management?

Other than that we are ready to go I think. The permission scheme in JIRA isnt straight-forward, however I think we have got a rather good grip on it now.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,166 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot