Details
-
Suggestion
-
Resolution: Fixed
Description
Parent issue for tasks coming out of the Blitz Test on jira-home and plugins2
Attachments
Issue Links
- details
-
JRASERVER-17626 Error message for omitting attachment path on Attachments admin screen is different to the error message during Setup
- Closed
-
JRASERVER-17627 Attachment path in Attachments admin screen allows non-absolute path
- Closed
-
JRASERVER-17628 Backup Service config prints jira.home instead of the actual path
- Closed
-
JRASERVER-17629 Error messages when loading an incompatible plugin could be better
- Closed
-
JRASERVER-17630 Message when startup failed could be improved
- Closed
-
JRASERVER-17631 When creating a home directory with an umlaut it showed up encoded wrong in the log.
- Closed
-
JRASERVER-17632 Safari alignment issues
- Closed
-
JRASERVER-17633 When running startup.bat from the command line, tomcat does not start, and no output it provided by the script.
- Closed
-
JRASERVER-17634 Backslashes in the jira-application.properties file.
- Closed
-
JRASERVER-17637 We seem to output some Unix only logging on Windows.
- Closed
-
JRASERVER-17640 The backup service configuration does not ensure that the backup directory is usable before saving its configuration.
- Closed
-
JRASERVER-17641 JIRA fails to start if it cannot create the plugins directory. The log message should be better.
- Closed
-
JRASERVER-17644 I made a 2.0 plugin in installed-plugins inaccessable (no permissions) to JIRA and restarted. I got this and a lovely 404 error:
- Closed
-
JRASERVER-17646 JIRA appears to freeze during shutdown when the index directory cannot be written to. This may just be slow shutdown.
- Closed
-
JRASERVER-17649 Adding an unsupported plugin in JIRA home "installed plugin" folder throw stack trace
- Closed
-
JRASERVER-17625 Error message on set up page for omitting index path does not have a full stop
- Closed
-
JRASERVER-17635 The path for attachments on JIRA setup page is not having correct slashes.
- Closed
-
JRASERVER-17636 Index screen in administration should not allow relative paths.
- Closed
-
JRASERVER-17639 Validating default directories before we move past the first setup screen.
- Closed
-
JRASERVER-17645 Get some log4j configuration errors in the Tomcat window when trying to close it using bin\shutdown.bat.
- Closed
- is related to
-
JRASERVER-17638 There is a warning about -XX:PermGen option not being valid when running JRocket. but it does not appear in logs
- Closed
- relates to
-
JRASERVER-17643 Having a stale index directory causes some logging weirdness.
- Closed