Details
-
Suggestion
-
Resolution: Won't Fix
-
None
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
This issue is not going to be addressed by the JIRA development team, but I wanted to provide some more detail about why. Most of the use cases described here are based on the desire to run arbitrary scripts in JIRA Cloud. Unfortunately, for security and performance reasons, this is something that we absolutely cannot support.
We have made significant investments in JIRA webhooks and the JIRA REST API in order to support executing the exact same actions remotely. Since we introduced Atlassian Connect in March 2013, this is the recommended integration architecture for Atlassian's Cloud applications. We have introduced a number of new REST API resources, with more coming in JIRA 7.0. There is also a new admin UI for administering and registering webhooks.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Many customers would like to implement an auto-close function similar to the one implemented on support.atlassian.com, but the one implemented by Atlassian requires the use of Jelly scripts, which are rightly banned from Cloud Applications as they have the potential to cause havoc or even allow a malicious user to perform a privilege escalation. However, the same function could be implemented by using Listeners to trigger a function, (such as the one in the bundled JIRA Toolkit plugin), so this feature request is to consider whether permitting any Listener functionality would be possible for Cloud Applications instances.
Attachments
Issue Links
- is duplicated by
-
- Gathering Interest
- is related to
-
- Closed
- relates to
-
- Gathering Interest
