Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Advice on writing our own front-end to Jira Service Desk (Cloud)? Edited

We like Jira Service Desk, but it doesn't have a few critical features that we want (namely, SSO/Okta integration for customers).

Because of this issue, we are exploring the idea of writing our own front-end to Jira Service Desk and integrating this new front-end with our existing private customer community site.  The plan is that customers would log in to our community site to try to search for a solution, if they can't find one, they can "open a support request" within the same customer community site.  They would never leave to go over to the JSD customer portal.

Thus, from the custom section of our community site, they could open a new support request.  The form submission would be processed by code that we write, and then communicate with JSD via RESTAPI calls to create the issue in JSD.

As part of this custom front-end, we're thinking of having these capabilities:

  • Create a new support request
  • View active support requests
  • View archived support requests
  • Add comments to existing support requests
  • Search support requests

Each of the above capabilities would utilize the JSD API.

Have other people done this before?  What issues/problems did you run into?

Here's what I'm worried about:

  • Can we use the API to create a JSD issue on behalf of someone else?
  • Can we use the API to create a comment on behalf of someone else?
  • What about syncing the customers from our existing community site to JSD?  Will the API let us create a customer sync and not send an email to the customer when their JSD customer account is created?
  • What about customer notifications when a service desk agent adds a customer visible comment?  Can we use the native JSD notification system for that and just be sure to remove the URLs that point to the *.atlassian.net site?  (We're using JSD cloud)
  • Other things that I haven't thought of but we're going to run into if we start building this.

Anyhow, any advice you have would be great.

Thank you,

Nathan

1 answer

Hi @Nathan Given ,

I think that developer community is better place for your question.

Regards,

Kate 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

182 views 1 6
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you