-
Suggestion
-
Resolution: Low Engagement
-
None
-
2
-
2
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
If we use JIRA CommentManager we can do this, if we use JSD we cannot.
Not being able to defeat events being fired means we cannot use the JSD Component API
- relates to
-
JSDSERVER-1505 Comments added to issues by addons are listed as internal by default
-
- Closed
-
-
-
- Closed
-
-
- Closed
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-3897] JSD Component API - need to be able create comments without firing events
Deleted Account (Inactive)
added a comment - Disappointing to see that this issue is still unassigned and has had no response from Atlassian. This lack of functionality causes problems for customers very regularly for us. Creating a comment without firing an event should be possible via the JSD comment API. There are cases where you would like to create comments silently without triggering a notification.
Deleted Account (Inactive)
added a comment - Disappointing to see that this issue is still unassigned and has had no response from Atlassian. This lack of functionality causes problems for customers very regularly for us. Creating a comment without firing an event should be possible via the JSD comment API. There are cases where you would like to create comments silently without triggering a notification. Hello,
Please could we have an updated response for this suggestion? @mmcmahon was able to do wonders with customer request type access via the JSD API recently, hoping that at some point some similar love could be applied here - it would remove our biggest development roadblock!
Thanks,
Mike
Just to clarify the current problem for any Atlassian's who look at this issue:
When creating comments via the JIRA API's CommentManager, its create() methods allow a dispatchEvent boolean to be set. This allows add-on developers to suppress the event at that point.
The JIRA Service Desk API however is not consistent. Its ServiceDeskCommentCreateParameters.Builder does not have a corresponding boolean that can be set to control event firing.
Rodney Frank
added a comment - Very Disappointed by the speed at which this issues is being addressed. Is there any further update at this time?
Rodney Frank
added a comment - Very Disappointed by the speed at which this issues is being addressed. Is there any further update at this time? Rodney Frank
added a comment - From an API perspective we have run into this similar problem with not being able to suppress the firing of events. It leads to notification spam as well. This is just for an internal page we are working on but when someone receives like 3-4 messages for just a single comment being created and updated by the API that is less than ideal.
Rodney Frank
added a comment - From an API perspective we have run into this similar problem with not being able to suppress the firing of events. It leads to notification spam as well. This is just for an internal page we are working on but when someone receives like 3-4 messages for just a single comment being created and updated by the API that is less than ideal. > Remember you can always use the JIRA API if/when that makes more sense.
Nope (remember JSD-1505 where solution there was to use JSD API ?). JSD will stamp ALL comments made through the JIRA API as Private, regardless of 'who' makes them, which is not what I want, and is why I needed to use the JSD API to make sure 'the right thing' happened regarding Public/Private.
Now I can (probably) do that through the API (just coded, not tested yet!) what I'm missing is a way to say 'hey' just create the comment but DONT fire an event, just like the JIRA API can. The reason for this is that I want to bundle up other changes as part of the event. I determine what event I want to fire later, it could be a ISSUE_COMMENTED or ISSUE_UPDATED, for example.
A further 'why' is that by inhibiting one event, when I know I'm going to send another, I can reduce email notifications, which is in everyones interest 
Actually, this is now a blocker for us to use the API yet as it would spam the users...
Andy, I'm assuming you mean JSD Comment API ? What's your use-case for this ? Remember you can always use the JIRA API if/when that makes more sense.
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion has had very low engagement over the past four years, with no new watchers, votes, or comments. As a result, we're closing it for now.
We understand that this suggestion might still be important to you. If you'd like to provide additional context or information about why it remains relevant, please contact our Technical Support team for assistance. We'll be happy to review your feedback.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center