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

Tempo products are disabled on JIRA 6.4 after restart

    XMLWordPrintable

Details

    Description

      Tempo Planner, Folio and Books are disabled on JIRA 6.4 after restart.

      We had to remove the JIRA 6.4 compatibility for these products. Is there a workaround that we can publish to our customers that they can use until a fix is released?

      It appears as everything works when we run our environment with atlas-run-standalone. Then if we restart it (just ctrl+C and run it up again) the products are not enabled. We have to manually install these plugins again in the UPM and that is quite sub-optimal.

      Additionally, JIRA 6.4 server is affected. We set up a JIRA 6.4 instance to verify that this problem was only limited to using the atlas-run-standalone command but the atlassian-jira-6.4.tar.gz file provided by Atlassian must be broken since we can access everything in the Admin section except the Add-ons section. There we get a 404 error despite having the correct URL.

      When one of our Timesheets developers first tried to see if the plugin worked on JIRA 6.4 last November, he experienced these difficulties and contacted Bradley Ayers from Atlassian. He gave us this answer:

      "After having a chat with the plugin system team, I've come to the conclusion that the 6.4-m09 milestone is broken, and it's something we'll need to fix before 6.4 final is released. If this is blocking your development (e.g. you need to test JIRA startup behaviour), there's a work around you can use until we fix this within JIRA:
      Make a copy of tenant-smart-patterns.txt, add your other plugin key to it, and then set the system property atlassian.plugins.tenant.smart.patterns to point to the new file."

      This workaround fixes our problems, but we thought that it should have been fixed by now. Can we do something else than this workaround? What should we tell our customers who are running our products on JIRA 6.4? Should we tell our customers to add the artifact ids to the tenant file as a short term solution?

      Thank you very much, I hope you understand that this is quite urgent.

      Attachments

        Issue Links

          Activity

            People

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              dbd838eb9e88 Ólafur Jens Ólafsson
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: