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!


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
Community Members
Community Events
Community Groups

How to access jira issue entity properties as a jira service desk customer user ?

Hi All,


We want to access issue entity properties as a Jira service desk customer user on the view issue page.


2 answers

1 accepted

0 votes
Answer accepted

When you want to share some of the information from the customer view to agent view or vice versa. you can use comment rest API. 

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 21, 2020

Hi Manish,

I understand that you are wanting to be able to use a Jira Service Desk customer account in order to be able to access and edit Entity properties via REST.

This is not possible to do with those specific account types.  The reason for this is explained in some more details in the Jira Server Developer documentation: Entity properties.  From that page

To modify, add, or remove the properties, the user who executes the request must have permission to edit the entity. For example, to add new property to issue ENPR-4, you need permission to edit the issue. To retrieve a property, the user must have read permissions for the entity.

Jira Service Desk customers are not licensed Jira users.  As such they don't use a license seat, so you can have an unlimited number of them.  However without at least first having application access, which in Jira Server is granted by having membership in a group that has that application access, such users can't even begin to see those issues in Jira itself.  They would also then need to meet the permission schemes requirements to be able to edit the issue itself.

Jira Service Desk affords unlicensed users in the customer role the ability to create requests, see their requests, comment, etc.  However the ability of those users to do that is restricted to only be possible within the customer portal, via the Jira Service Desk mail handler, or via the Jira Service Desk REST API.  All of these methods though are meant for the customers to interact with the request, but not the issue itself in Jira.   More on this distinction between Issues vs. Requests in Jira Service Desk: Issues vs. Requests.

Sorry this is probably not the answer you were looking for, but I at least hope this helps to explain the behavior here.



Thank you @Andy Heinzer 
I solve my problem by using a comment. 

Like Andy Heinzer likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events