Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-71831

3rd party automation apps cannot be enabled if they were installed prior to Automation for Jira

      Issue Summary

      3rd party automation apps cannot be enabled if they were installed prior to Automation for Jira.

      Steps to Reproduce

      1. Install and start Jira Server 8.13.1
      2. Clone and build the Atlassian 3rd party sample app from here: https://bitbucket.org/atlassian/automation-addon-sample/src/master/automation-thirdparty-sample/
      3. Install the sample app JAR into Jira. An exception is thrown and the app becomes disabled.
      4. Install Automation for Jira 7.2.1 app into Jira from here: https://marketplace.atlassian.com/download/apps/1215460/version/300003990
      5. Try to enable the sample app. It hangs and won't enable.

      Expected Results

      The sample app can be enabled once Automation app is available.

      Actual Results

      The sample app cannot be enabled. It hangs for a while then remains disabled.

      Workaround

      A possible workaround is reinstalling the sample app, but this is still very confusing and frustrating for new customers.

            [JRASERVER-71831] 3rd party automation apps cannot be enabled if they were installed prior to Automation for Jira

            Ferenc Nagy added a comment - - edited

            Based on he Atlassian SDK developer documentation, we managed to solve the problem by making the asterisk optional, like:

            <Import-Package>
             ...
             *;resolution:="optional"
            </Import-Package>

            https://developer.atlassian.com/server/framework/atlassian-sdk/configuration-of-instructions-in-atlassian-plugins/#making-the-wildcard-optional

            Could you confirm that it's the correct solution?
            If so, please update the sample app according to this.
             

            Ferenc Nagy added a comment - - edited Based on he Atlassian SDK developer documentation, we managed to solve the problem by making the asterisk optional, like: <Import-Package> ... *;resolution:= "optional" </Import-Package> https://developer.atlassian.com/server/framework/atlassian-sdk/configuration-of-instructions-in-atlassian-plugins/#making-the-wildcard-optional Could you confirm that it's the correct solution? If so, please update the sample app according to this.  

              Unassigned Unassigned
              dmorrow@atlassian.com Dugald Morrow
              Affected customers:
              6 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: