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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,358
Community Members
 
Community Events
184
Community Groups

When a customer creates a Jira service desk ticket, the organization field is empty

When a customer of ours who has access to Jira Service Desk Portal creates a new Jira ticket,the organization field is not set to that of the reporter automatically.

Previously when we received tickets from customers, the organization field would point to the reporter belonged organization.

I can confirm this by creating a Jira Service Desk ticket and by leaving the Organization field to "No one" - which is the default in our JSD customer accessible portal.

Please refer to screenshots

Screen Shot 2022-10-06 at 11.48.03 am.png

 

Notice how it shows up on the Agent view when created with "Share with XYZ organization" and "No one" selected on the other instance.

Screen Shot 2022-08-18 at 1.13.36 pm.png

We have no abiity to edit the "Request type" forms to force specify the reporter's or raised "on behalf of's" organization. Certain automation rules of ours rely on organization and this is causing issues upstream.

Can you please let us know how Organization can be forced when a Jira Service Desk ticket is created?

This is quite important to us and we look forward to your attention and a resolution on this issue.

2 answers

1 accepted

2 votes
Answer accepted
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 05, 2022

@Prasanna Subramanian -

You will need to ensure that the the Products (JSM) configuration is setup as followed (NOTE - this is a global setting for the JSM product)

1) Access https://<your site>.net/jira/settings/products/jira-service-management-configuration UI.

2) In the following section, the "Yes" choice should be checked.

2022-10-05_18-20-49.png

NOTE - If the above setting is setup, then it will default the Share with to the Org.  The issue reporter can still change it to "No One".

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Cheers @Joseph Chung Yin for your prompt response. I was able to find the page albeit some changes to the link you shared. Here is the updated link.

https://REPLACE_WITH_YOUR_ORG.atlassian.net/jira/settings/products/jira-service-management-configuration

Appreciate it and after making the highlighted change in the second step of yours, I reloaded the customer portal Form and now it default to the "Share with XYZ" dropdown value.

Like John Funk likes this

This cannot be accurate.  The only way to ensure the system automatically associates a Ticket entry to the Organization raising that ticket is to inform the entire Organization of the event?  Is automation the way to go to make this work in a better fashion?

-Troy

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events