Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


JSM create screen toggle "Use request type fields" affects REST API calls



so as I just discovered, opening the create screen in the UI and toggling the "Use request type fields" on/off and then closing the screen again without creating an issue actually dictates which fields are required for rest api calls to endpoint "rest/api/2/issue".

I couldn't find anything about that in the documentation and I couldn't find a way to actually add a json key and value to the REST calls to make sure the backend fields are used, and not the customer portal fields (which have different required fields in out setup) .

I had to actually flip this switch in the UI, which I discovered on a wild hunch as I was desperately trying to figure out why I get blocked by customer portal field requirements.

My expectation was that "rest/api/2/issue" always uses the backend fields as it is not a JSM endpoint and if any endpoint was going to be using the customer portal fields instead then it would have been "rest/servicedeskapi/request", but this is not the case, it seems.

I have not tested how "rest/servicedeskapi/request" behaves yet. So maybe somebody could share their knowledge here if it simulates the customer or agent creation process.

So this post is about raising awareness and asking if there is a way to set this within one of the issue creation REST calls or maybe if there is a different call entirely to set this flag.




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events