-
Suggestion
-
Resolution: Answered
-
None
-
None
-
None
Currently, the atlassian-greenhopper.log seems to be hardcoded into the plugin source, making it hard for an administrator to modify it's location or name.
It should work like JIRA's log that is configurable through the log4j.properties file.
Form Name |
---|
[JSWSERVER-9911] Allow administrators to configure name and location of log file
Workflow | Original: JAC Suggestion Workflow [ 3066655 ] | New: JAC Suggestion Workflow 3 [ 3657804 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2626144 ] | New: JAC Suggestion Workflow [ 3066655 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2321263 ] | New: Confluence Workflow - Public Facing v4 [ 2626144 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2040560 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2321263 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2029131 ] | New: JIRA PM Feature Request Workflow v2 [ 2040560 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 733893 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2029131 ] |
Workflow | Original: GreenHopper Kanban Workflow v2 [ 560254 ] | New: JIRA PM Feature Request Workflow v2 [ 733893 ] |
Issue Type | Original: Task [ 3 ] | New: Suggestion [ 10000 ] |
Priority | Original: Minor [ 4 ] | |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Answered [ 9 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Affects Version/s | Original: 6.3.2.1 [ 37207 ] |