Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-36046

Provide REST API for running SQL queries directly on the database

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      It would be great, and easy to implement, and rest function that could be used by jira-administrators to run SQL queries (SELECTs) directly on jira database.

      This could be used to gather data from JIRA database in many use-cases where current REST api does not support it.

      Considering that this is read-only and that the JIRA database structure is quite stable having this makes a lot of sense.

      This could also be used to implement very interesting stats just with JavaScript.

            [JRACLOUD-36046] Provide REST API for running SQL queries directly on the database

            Sorin Sbarnea added a comment -

            I am wondering why this would be as a security hole, as long is properly implemented (not allowing other actions than select). Clearly passwords cannot be exposed because they are not in plain text and obviously it would be limited to a certain group of users, probably jira administrators.

            Now regarding the instability of the database schema, based on the experience of Jira 3.x-6.x I would say that is quite stable and there is no much difference between the number of changes in APIs (SOAP / REST) and the database schema.

            Anyway, you have a point regarding possibility to implement it as a plugin.

            The only thing that I do not like is that by closing the ticket you prevent people from voting on it.

            Sorin Sbarnea added a comment - I am wondering why this would be as a security hole, as long is properly implemented (not allowing other actions than select). Clearly passwords cannot be exposed because they are not in plain text and obviously it would be limited to a certain group of users, probably jira administrators. Now regarding the instability of the database schema, based on the experience of Jira 3.x-6.x I would say that is quite stable and there is no much difference between the number of changes in APIs (SOAP / REST) and the database schema. Anyway, you have a point regarding possibility to implement it as a plugin. The only thing that I do not like is that by closing the ticket you prevent people from voting on it.

            Matt Quail (Inactive) added a comment -

            There would be some security concerns for sure. Also, our SQL tables are not "stable" and hence we couldn't really offer a stable API.

            This should be wont-fixed.

            People who have this usecase could write a P2 plugin that exposed such an interface. Admins could then install it as they see fit. It would make a good marketplace plugin actually.

            Matt Quail (Inactive) added a comment - There would be some security concerns for sure. Also, our SQL tables are not "stable" and hence we couldn't really offer a stable API. This should be wont-fixed. People who have this usecase could write a P2 plugin that exposed such an interface. Admins could then install it as they see fit. It would make a good marketplace plugin actually.

            Josh Devenny added a comment - - edited

            mquail - I suspect this would be a VERY large security hole and we'll never do it?

            Josh Devenny added a comment - - edited mquail - I suspect this would be a VERY large security hole and we'll never do it?

              Unassigned Unassigned
              5fa3fdf29175 Sorin Sbarnea
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: