Is it possible to create issues for Service Desk Customers?

We would like to be able to create issues for our (existing, already signed up via the portal) Service Desk Customers. While we are transitioning to using Service Desk, we still get phone calls at times and would like to be able to create those issues for our customers.

I know that we can create issues in the JIRA Service Desk project, and that we can also even set the reporter to one of the Service Desk Customers, but there doesn't seem to be a way to make those issues appear in the "My Requests" list when that customer logs into their portal (even setting the reporter to be that customer does not do this).

Another use case here is migrating from our other existing issue tracking messages. For instance, we already have quite a few "issues" in Asana, but would like to be able to recreate those for our customers in Service Desk, and allow them to continue tracking progress on them via the portal.

3 answers

1 accepted

Thanks Joel, I think that is the best solution for this issue (having it fixed).

In order for an issue to show up in the customer portal, a field called "Customer Request Type" must be set. This is not a field that JIRA exposes natively, but here are two ways to set it with add-ons.

Option 1:

If you are not OnDemand, the Automation plugin can set the Customer Request Type for you when the issue is first created. To do this, first set up a Trigger, e.g.:

  • Type: Issue Event Trigger
  • Issue Event: Issue Created
  • JQL expression: project = NSD AND “Customer Request Type” is EMPTY


And then set up the Action you want to take place:

  • Edit fields: customfield_10451=nsd/get-it-help
  • Allow variable expansion: No
  • Send notification? No


(Find the custom field ID by going to your Custom Fields page, then click the cog next to Customer Request Type and hover over Configure.)

Option 2:

You can also do this with JIRA Suite Utilities; you’d set a post-function on Issue Create to Update Issue Custom Field, modifying Customer Request Type to be the appropriate value, e.g.:

  • nsd/get-it-help

Thanks for these ideas, I may try them out while we wait for JSD-55 which Joel mentioned.

what you can try is create the issue through the customer portal then change the reporter to them.

That requires having the user's password, but I suppose we could create the account then pass it off when we have migrated things. This might work in some scenarios, thanks for the idea.

well not using their account use yours then change it to them

This will not help, the issue does not show up in the customers portal, the only way it shows up is if the issue was created through the portal with the customers credentials

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

752 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