Obstacles to joining Service Desk 2.0: Customers not accessing JIRA view

Service Desk 2.0 is potentially a savings for me, but there are still some 'workaround' whereby I have to send Customers to JIRA view to allow them to perform a number of operations. Given that with the new model Customers wouldn't be able to use JIRA anymore, I need to ensure they have everything they need in Service Desk.

Maybe people will want to chip in and list the number of open suggestion tickets that are currently with Atlassian, but these are my key ones:


I wondered whether Atlassian had any ETA, or whether the community also considered these lack of features as obstacles. Note i am on Demand.

2 answers

Hi Laurence, 

Thanks for all the suggestions. These are very important to us specially coming from our customers. smile

About an ETA time, I'd encourage you to take a look over  [Implementation of New Feature Policy|https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy] for more information on Atlassian's approach to the development of these improvements.

Please let us know if we can help you any further.


Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Dec 06, 2018 in Jira Service Desk

Looking for teams who switched from email to Jira Service Desk

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...

807 views 6 10
View question

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