Issues
- Change way of setting a mail server password for distributed configurationsBAC-1416Resolved issue: BAC-1416
- Add "Link Issues" to permissions in connection tabBAC-1238Resolved issue: BAC-1238
- Show list of synchronizations even if one connected instance is not reachableBAC-1235Resolved issue: BAC-1235
- Add multiple comments with a minimum waiting time to avoid missed commentsBAC-1233
- Reuse sprints from whole Jira instanceBAC-1229Resolved issue: BAC-1229
- Add prefix to sprint name when syncing sprintsBAC-1228Resolved issue: BAC-1228
- Improve field mapping matching of fields with the same nameBAC-1227
- Issue links in troubleshooting may point to the wrong locationBAC-1226Resolved issue: BAC-1226
- Project is not selectable if a slave synchronization is createdBAC-1214Resolved issue: BAC-1214
9 of 9
Change way of setting a mail server password for distributed configurations
Duplicate
Description
Environment
None
Created June 29, 2020 at 2:21 PM
Updated February 15, 2023 at 4:41 PM
Resolved March 19, 2021 at 3:56 PM
Activity
Show:
Liset de Bruin (K15t) March 19, 2021 at 3:55 PM
We are closing this ticket as we have another ticket that covers this issue. You can find the issue here: https://k15t.jira.com/browse/BAC-1417 .
At the moment a password for a mail server is configured using a URI. This is a Camel supported feature. However, such a URI does not accept all kinds of special characters and thus might fail for e.g. # or something else. We've already fixed a bit in [BAC-1203|https://k15t.jira.com/browse/BAC-1203] , but not everything is fixed.