Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-83

Allow project administrators to import rules via JSON

XMLWordPrintable

    • 0

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

      Problem Definition
      Project administrators do not currently have a way to copy rules between projects and import from JSON definitions.

       

      Suggested Solution
      Allow JSON rule imports into a specific project by project administrators.

       

      Why this is important
      Offloads the effort to project administrators, and allows them to easily share rule definitions with other teams to increase collaboration.

       

      Workaround
      No workaround as of now.

            [JIRAAUTOSERVER-83] Allow project administrators to import rules via JSON

            Marc Dacanay made changes -
            Labels Original: iq-a4j New: iq-a4j ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 978963 ]
            Lacey McDonnell made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 897579 ]
            Lacey McDonnell made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 890075 ]
            Lacey McDonnell made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 887611 ]
            Lacey McDonnell made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 882824 ]
            Lacey McDonnell made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 880517 ]
            Lacey McDonnell made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 878950 ]

            Michael Mitschke added a comment -

            Like other things which are missing: this is a no brainer to add.
            Sorry if I might come accross rude but sometimes I really feel whoever is testing Jira should develope a new way of doing so...

            Michael Mitschke added a comment - Like other things which are missing: this is a no brainer to add. Sorry if I might come accross rude but sometimes I really feel whoever is testing Jira should develope a new way of doing so...

            Adam W. Nichols added a comment -

            This would be a very useful feature - we have > 10 teams in our newly-launched Product (and counting), and automation is key to maintaining a degree of standardization in our development processes. Re-deploying all of the automation rules to each project is time-consuming, error-prone, and stifles change, because of the amount of work involved every time an update is needed. The Automation feature is powerful today, but could be so much better.

            Adam W. Nichols added a comment - This would be a very useful feature - we have > 10 teams in our newly-launched Product (and counting), and automation is key to maintaining a degree of standardization in our development processes. Re-deploying all of the automation rules to each project is time-consuming, error-prone, and stifles change, because of the amount of work involved every time an update is needed. The Automation feature is powerful today, but could be so much better.

              Unassigned Unassigned
              f1abf08a593a Joe Otis
              Votes:
              88 Vote for this issue
              Watchers:
              39 Start watching this issue

                Created:
                Updated: