That's very much needed. We have several integrations where agents from other systems write comments from there

and they get as commenter some Jira helper and it is quite confusing

@Tushar Wagh 

Is there any updates on this ?

I doubt there will be any update on this as EOL is nearing: https://www.atlassian.com/migration/assess/journey-to-cloud

Is there any updates on this ?

One year more and we will have 10th anniversary. :tada

Tell me, why can't i wrote my own email handler posting comments on behalf different users? Can't do this , can't do that - this product is disappointing as f*&^ !

Ps. I am not going to buy email handler plugins since they are billed per seat!

I don't believe that Atlassian will ever add this feature because the current way to get around it is to purchase licenses for all users. If they added this functionality that would no longer be necessary.

That said, this basic missing functionality was a deal breaker for us. We wanted to make our own in house issue tracking system using the Jira Api, but we ended up creating our own api because of this problem. Extremely frustrating.

I have app that integrated with jira,

the user of my app can't comment on Jira via my app from their own name, because I does not have their passwords in domain

I need this feature asap

We have fully integrated JSD into our Magento 2 application. We sell Magento extensions and use the integration to directly support our customers in our website without them having to worry about any internal systems we use. It simplifies things for our customers and simplifies it for us aswell because customer tickets are created in JSD and automatically added to our KANBAN board. 

This being said, we can create a request ticket on behalf of a customer just fine. The customer creates an account in our shop and as soon as the customer wants to raise its first request, a customer in JSD is created and the request is raised.

It only seems logical that i can use the customers accountId, which we get in the response from creating a new customer, to create a comment on his or hers behalf. It really baffles me that this is impossible at the moment, as this seems 100% logical follow-up behavior which is in line with being able to create a ticket on behalf of this customer in the first place. If you can create a request on behalf of the customer, why cant you work with that request on behalf of that same customer to create things like comments?

I really need to be able to provide "raiseOnBehalfOf" in the request headers for comments and possibly the other request endpoints aswell, so that this works in line with the request creating.

Not having this feature already costed us a lot of support because customers file complaints against us, complaining how we respond with their texts in their name. Simply because when we create the comment, the only way for us to create a comment is under our own name. It also costed us money because when the comment is raised under our own name, the ticket is transitioned but no notifications are being sent to us and this causes the customer to wait for support or answers until we notice it. If this process takes to long, the customer wants a refund which happened on multiple occasions.

Can you please give this priority, it has 303 votes and i'm more than willing to pay a few hours of support to get this implemented, if that's what it takes to get this to progress faster. This problem is affecting us as a company for about a year now so i would love to get this feature implemented

@jacqueline Sudo for Jira is continuing to be updated, but as was indicated earlier in the thread, it is not currently compatible with the Cloud version of Jira.

This function is an absolute basic requirement for all companies that use their own customer portal and only pass the issues backwards via the api. Currently you can only use the plugin sudo for jira, which is no longer updated. This function is a must, if you already have the create ticket on behalf of function, why is such a mandatory api function missing?

Thanks for suggestion but unfortunately we use Jira Cloud which doesn't appear to be supported.