Log inSkip to main contentSkip to sidebar
Loading…
Jira
  • Dashboards
  • Projects
  • Issues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • Issue Reminders help
    • About Jira
    • Jira Credits
  • Log In

Export - CSV (All fields)

Export - CSV (Current fields)

Comma (,) Semicolon (;) Vertical bar (|) Caret (^)

  1. Bug MXS-3474
    Strange persistent pool connection stats
  2. Bug MXS-2730
    Connection attributes are not passed on
  3. Task MXS-1078
    Refactor dbusers.c
  4. Bug MXS-2593
    Fake hangups from backend DCBs cause worker messages to be emitted
  5. New Feature MXS-1635
    Allow binding of the backend IP address
  6. Bug MXS-249
    Questionable error messages from backend connections
  7. Bug MXS-5402
    Monitor connections do not check SSL certificate host even when ssl_verify_peer_host is enabled for the server
  8. New Feature MXS-4951
    Support server side ephemeral certificates
  9. Task MXS-4731
    COM_CHANGE_USER support for all authenticators
  10. Bug MXS-4723
    Passthrough authentication does not support COM_CHANGE_USER
  11. Bug MXS-5556
    Trailing parts of large session command are not routed correctly
  12. Bug MXS-5536
    Early mismatched responses to session commands do not close connections
  13. New Feature MXS-4774
    Add support for ephemeral server certificates
  14. Bug MXS-3427
    The 'INFORMATION_SCHEMA.SESSION_STATUS' feature is disabled; see the documentation for 'show_compatibility_56'
  15. Bug MXS-3426
    MaxScale with SSL in Azure Cloud not working properly
  16. Bug MXS-5142
    Workaround Maxscale Not Distributing the load on all Galera Cluster nodes equally
  17. Bug MXS-5134
    Maxscale Not Distributing the load on all Galera Cluster nodes equally
  18. Bug MXS-3110
    bad handshake error in maxscale 2.5.1
  19. Bug MXS-3101
    getpeername()' failed on file descriptor
  20. Bug MXS-4230
    Maxscale doesn't match regex user's host
  21. Bug MXS-3328
    Persistent Connections on Maxscale 2.5 seem to break client authentication
  22. Bug MXS-3292
    Unable to execute use `database`
  23. Task MXS-3265
    Better Connection Pooling and multiplexing - Phase 1
  24. Bug MXS-3203
    Persistent connections prevents Galera node to stop/restart
  25. Bug MXS-2511
    Maxscale c-connector version
  26. Bug MXS-1109
    Routing many prepares statements gives "#HY000Lost connection to backend server"
  27. New Feature MXS-1552
    Global thread id
  28. New Feature MXS-1550
    Proxy side net_write_timeout and net_read_timeout
  29. New Feature MXS-1548
    Shared connection
  30. Bug MXS-1462
    MaxScale erroneously connects to MySQLBackend servers via TLS1.0 rather than TLS1.2
  31. Bug MXS-2598
    memory leak on handling COM_CHANGE_USER
  32. New Feature MXS-2145
    new options prequery_sql_file and connection_sql_file
  33. Bug MXS-2961
    Connection fails with ssl=true and MariaDB 10.1.44
  34. Bug MXS-2216
    Read past stack buffer
  35. Bug MXS-1718
    Authentication failures leak memory
  36. Task MXS-1603
    Get trx status from ok packet through SESSION_TRACK_TRANSACTION_STATE mechanism
  37. Task MXS-1596
    Rename mysqlbackend to mariadbbackend
  38. Task MXS-1303
    Test proxy protocol as soon as 10.3 alpha is available.
  39. Bug MXS-2066
    Result buffering is not always disabled
  40. New Feature MXS-719
    Ability to specify outgoing port range
  41. New Feature MXS-381
    support for transparent proxy
  42. Bug MXS-372
    Setting client character set after connection has no effect
  43. Bug MXS-365
    Load data local infile connection abort when loading certain files
  44. New Feature MXS-334
    Enable Pam.d Support
  45. New Feature MXS-129
    Develop Client Side SSL support for MaxSCale
  46. Bug MXS-619
    creating many short sessions in parallel leads to errors
  47. Bug MXS-593
    Load data local infile returns before completion
  48. New Feature MXS-5990
    Set TLS Server Name Indication for backend connections
  49. New Feature MXS-651
    SSL for backend connections
  50. Bug MXS-6049
    Low persistpoolmax should cause log warnings/errors
Refresh results
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
0.3
0
  • Atlassian Jira Project Management Software
  • About Jira
  • Report a problem

Powered by a free Atlassian Jira open source license for MariaDB Corporation Ab. Try Jira - bug tracking software for your team.

Atlassian