| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 6 |
|---|
| outline | false |
|---|
| style | none |
|---|
| type | list |
|---|
| printable | false |
|---|
|
Scenario
| Status |
|---|
| colour | Yellow |
|---|
| title | SINCE 4.1.35 |
|---|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | SINCE 4.2.0 |
|---|
|
The limits, CommentCountLimit and CommentMaxCharsLimitComment count limit and Comment char length limit, have moved from Profile Config > Issues into Profile Config > Project-mappings > edit project-mapping > email filters. However, the implementation of the limits has a bug in certain versions that allows users to enter -1 values in the default project-mapping, which is an illegal character for the default project-mapping.
| Info |
|---|
For more information on CommentCountLimit and CommentMaxCharsLimitComment count limit and Comment chars length limit, visit https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/3801939983/Email+Project+Mapping#Comment-count-limit |
Work around
...
for versions 4.1.35-4.1.41 and 4.2.0
The work around is to not enter -1 as the CommentCountLimit and CommentMaxCharsLimit.
The work around applies to the following versions:
All versions between 4.1.35 and 4.1.41
4.2.0
Versions of JEMH that fix the bug: from 4.1.42 and from 4.2.1
| Status |
|---|
| colour | Yellow |
|---|
| title | since 4.1.42 |
|---|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | Since 4.2.1 |
|---|
|
-1 is no longer a valid value for Comment count limit and Comment char length limit in the following versions: