-
Bug
-
Resolution: Duplicate
-
Low
-
2.3, 2.3.2, 2.3.3, 2.3.4, 2.3.5
The message threshold limit needs to be set to 0 in our configuration (otherwise we experience the BAD error described here: https://confluence.atlassian.com/display/JIRAKB/BAD+Command+Argument+Error+when+creating+issue+via+email+with+Microsoft+Exchange) I just upgraded JIRA from 6.4.1 to 6.4.2 and the threshold limit was reset to 5 which caused the error to return. I reported the same issue whenever a JIRA Service Desk upgrade was performed: https://jira.atlassian.com/browse/JSD-1747
- duplicates
-
JSDSERVER-3112 JIRA application restarts reset the Message Threshold in JIRA
-
- Closed
-
Form Name |
---|
[JSDSERVER-3113] JIRA upgrades reset the Message Threshold limit in the Advanced mail loop detection configuration
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304504 ] | New: JAC Bug Workflow v3 [ 3125023 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2058685 ] | New: JSD Bug Workflow v5 - TEMP [ 2304504 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056765 ] | New: JSD Bug Workflow v5 [ 2058685 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1956545 ] | New: JSD Bug Workflow v5 - TEMP [ 2056765 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1616207 ] | New: JSD Bug Workflow v5 [ 1956545 ] |
Labels | Original: slush | New: affects-server slush |
Workflow | Original: JSD Bug Workflow v2 [ 1603414 ] | New: JSD Bug Workflow v4 [ 1616207 ] |
Workflow | Original: JSD Bug Workflow [ 1399391 ] | New: JSD Bug Workflow v2 [ 1603414 ] |
Workflow | Original: TTT: Simple Issue Tracking Workflow [ 1027636 ] | New: JSD Bug Workflow [ 1399391 ] |
Fix Version/s | New: 2.4.1 [ 53595 ] | |
Fix Version/s | Original: 2.3.6 [ 53592 ] |