Details
-
Sub-task
-
Resolution: Fixed
-
High
-
None
-
None
-
None
Description
JIRA does not allow specifying attachments path and index path. But we believe these are overwritable by changing some properties in jira-application.properties.
But Studio has been using different paths than the default ones.
We need to investigage
- whether there is any security risk in Studio if we use specified paths.
- if we decide to use the default paths, does JIRA provide an upgrade task to copy the contents over for attachments? For the cached index, do we need to trigger the index?
- if we decide to continue using customised paths, we'll need to modify jira-applicaiton.properties and change our func test accordingly. (currently it's changed to use the default path so that we can make the tests pass, I believe.)
Attachments
Issue Links
- blocks
-
CLOUD-3378 TestStudioSearch is broken after the upgrade (many tests)
- Closed
-
CLOUD-3389 Fix TestJiraUpgradeSimple.testAttachmentsInCreateIssueScreen()
- Closed
- is blocked by
-
CLOUD-3697 Add an upgrade task to change existing instances to using the default directories for attachments and indexes
- Closed
- is caused by
-
CLOUD-3668 Support fallback to default paths
- Closed
- is related to
-
CLOUD-3409 Contegix to change indexes and attachment paths to default paths in database templates for new instances
- Closed
-
CLOUD-3410 Contegix to move the indexes and attachment paths to default paths for existing instances to the default paths
- Closed
-
CLOUD-3411 Change jira test xml data to be using the default paths for attachments and indexes
- Closed
-
CLOUD-3412 Document the JIRA default paths issue when restoring a back up created before upgrading to Studio 2.4 (JIRA 4.2) for supports
- Closed