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-5403
    Debug assertion on very large binary protocol prepared statements
  2. Bug MXS-5269
    Unexpected response after failed session command
  3. Bug MXS-5266
    Query canonicalization does not take SQL mode into account
  4. Bug MXS-5234
    webpack warns about yargs
  5. Bug MXS-5382
    Errors due to max_connections being exceeded are always fatal errors
  6. Bug MXS-5364
    Allow monitor ssh-parameters to be modified at runtime
  7. Bug MXS-5359
    Transaction replay may deadlock with switchover
  8. Bug MXS-5357
    Improve MariaDB Monitor documentation on auto_failover and auto_rejoin
  9. Bug MXS-5412
    SET tx_isolation cancels out strict_multi_stmt and strict_sp_calls
  10. New Feature MXS-5299
    SUID sandbox support for admin_pam_readonly/readwrite_service
  11. Bug MXS-5402
    Monitor connections do not check SSL certificate host even when ssl_verify_peer_host is enabled for the server
  12. Bug MXS-5378
    Nested listener parameters depend on protocol being defined
  13. Bug MXS-5377
    Debug assert if backend fails during multi-packet query
  14. Bug MXS-5374
    Kafkaimporter doesn't work with MariaDB 11
  15. Bug MXS-5372
    timeout in kafkacdc is not a duration type
  16. Bug MXS-5366
    Certain special characters in the maxscale user causes async-rebuild-server to fail
  17. Bug MXS-5361
    Query editor: Column visibility filter shows wrong checkboxe values after search
  18. Bug MXS-5356
    Readwritesplit master_reconnection is incompatible with GET_LOCK
  19. Bug MXS-5355
    Switchover may cause two transaction replays to be started
  20. Bug MXS-5353
    MaxScale 24.02.3 fatal signal 6 after mariadb master is down
  21. Bug MXS-5351
    XA ROLLBACK is not treated as a rollback in MaxScale
  22. Bug MXS-5350
    XA END is treated as the transaction commit instead of XA PREPARE
  23. Bug MXS-5349
    Relay log write failure
  24. Bug MXS-5344
    Kafkaimporter constraint makes it difficult to use with kafkacdc
  25. Bug MXS-5341
    User account manager hangs on shutdown
  26. Bug MXS-5414
    Option --export-config does not work as documented or in any useful manner
  27. Bug MXS-5408
    rebuild-server does not work with MariaDB 11.4
  28. Bug MXS-5401
    absolute path to maxctrl.js in binary tarball bin/maxscale script
  29. Bug MXS-5399
    Maxscale crashing
  30. Bug MXS-5397
    NVL and NVL2 are not detected as builtin functions outside of sql_mode=ORACLE
  31. Bug MXS-5394
    Empty passwords are shown as non-empty if password encryption is enabled
  32. New Feature MXS-5388
    Feature Request: Support for Client Certificate Passthrough in MaxScale
  33. Bug MXS-5302
    Prepared statements should never be removed from session command history
  34. Bug MXS-5301
    SQL Errors detected when restarting maxscale.
  35. Bug MXS-5273
    The --config-check fails if /var/cache/maxscale cannot be read
  36. Bug MXS-5258
    delayed_retry should not retry interrupted writes
  37. Bug MXS-5256
    SET statements multiple values are not parsed correctly
  38. Bug MXS-5248
    Debug assertion due to non-existent dcall ID
  39. Bug MXS-5239
    Listener with ssl=false allows user accounts created with REQUIRE SSL to log in
  40. Bug MXS-5229
    Master Stickiness status not displayed correctly with use_priority
  41. Bug MXS-5339
    Slow servers may cause OOM situations if prepared statements are used
  42. New Feature MXS-5230
    Add a way to configure the preference of servers
  43. Bug MXS-5608
    optimistic_trx causes a query to hang
  44. Task MXS-5389
    Build maxctrl as an executable
  45. Bug MXS-5387
    Crash in MariaDBParser::Helper::get_query_info()
  46. Bug MXS-6033
    No error or warning when using an unreadable PAM config
  47. Bug MXS-5947
    Fix for MXS-5196 can break "maxctrl create report"
  48. Bug MXS-5450
    maxctrl list queries fails
  49. Bug MXS-5332
    The /var/lib/maxscale/maxscale.cnf.d should be a part of the packages
  50. Bug MXS-5265
    Strange behavior of admin_pam_readwrite_service
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