Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

Hi All,

Requirement: 

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

Cheers,

Andy

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
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

314 views 9 7
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