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

Allowing SetupImport to use either "absolute path" or "JIRA.HOME" as a base to find an import file can lead to confusion.

XMLWordPrintable

    • 4.02
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 16 November 2017

      Hi everyone,

      The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low.
      Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out.

      Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments.

      Cheers,
      Ignat Alexeyenko
      Jira bugmaster.

      Show
      Atlassian Update – 16 November 2017 Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out . Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster.

      In response to JRADEV-2997 we now do this on the SetupImportAction to locate the import file:

      1. Locate the file using the path as entered by user. Relative paths will be based at Tomcat working directory. Absolute paths will be honored. If file is found then restore otherwise continue to next step.
      2. Locate the file using $JIRA.HOME/import as the base. For this check we strip the path from the file and just look for $JIRA.HOME/import/$FILE.

      This can cause confusion if the user is trying to restore a file located using 1, but they actually restore a file using 2. For example:

      1. Adam has a file called $JIRA.HOME/import/backup.xml.
      2. Adam tires to restore c:\tmp\backup.xml when he actually meant c:\temp\backup.xml.
      3. [BUG] JIRA rather than returning in error restores $JIRA.HOME/import/backup.xml without any indication this what it decided to do.

      As a user I find this very strange behavior. I would expect an error or at the very least a confirmation before trying to restore $JIRA.HOME/import/backup.xml as it is not the file that I typed in. We may even want to consider skipping the $JIRA.HOME/import lookup altogether if the user types in a file with any path. Finally, it may also be useful to indicate which file JIRA was restored from both in the server log and on the import result screen.

          Form Name

            [JRASERVER-22772] Allowing SetupImport to use either "absolute path" or "JIRA.HOME" as a base to find an import file can lead to confusion.

              Unassigned Unassigned
              bbain bain
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: