1) Have all items come in as an default user and capture the users contact name info
2) Tie it with JEMH to handling the communication aspects of it
JEMH was built to handle these kind of requirements around limiting license costs and still being able to communicate with customers. All items coming in would be a "Automation User" but if you have JEMH setup up right, you'll be able to intake mail and communicate out about it.
Is SD perfect? No. It's v1. But it solves a lot of problems for folks and there are ways around things with out bending the tools too out of shape.
Also noticed that ondemand licenceing would be quite expensive as you have to buy a full jira seat and and agile seat (if you are using that) as well as service desk seat.
So if I wanted to add 100 external users it would cost me $600 a month.
I really hope the SD vNext moves to be able to be used as a Zen or desk.com replacement as its in a prime postion to do so.
Same question here
More specifically I was wondering whether :
* a user that logs a request needs to be part of the licensed Jira user on the Service desk system
* on the customer portal : a customer is able to check the list of previous requests made by other members of his team?
* multiple customers can be handled through the same Jira Service Desk project but without these customers having access to issues from other customers?
* the customer portal "my request" list can be further customized (eg. showingFixVersion)?
* the customer portal "view request"form can be further customized (eg more actions the "Add comment")?
I agree with Marcus, this is getting very expensive - we have an internet facing JIRA with autocreation of users - currently approx. +1500 users - where only someting like 500 are active or "new", the rest are old, spam or systems mailing in.
The SD pluging will cost us $12000 + the JIRA license - way to expensive for a 25 man company, so we extract JIRA data to splunk to get the same SLA data. And looking into OTRS or ZenDesk as replacement
Finally, this is actually what JIRA has been missing, so I am sad its not a general part of JIRA, or way cheaper/different license model for pulic JIRA's
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
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!
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