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. New Feature MXS-463
    .secret file path has double slash
  2. Bug MXS-442
    COM_PING is sent to all servers
  3. Bug MXS-390
    Lack of checks of dynamic memory allocation
  4. New Feature MXS-389
    Please statically link maxbinlogcheck (and maybe other cli utilities)
  5. Bug MXS-380
    Upgrade overwrites existing /etc/maxscale.cnf
  6. Sub-Task MXS-320
    Mention Unknown Filters in Error Log
  7. New Feature MXS-302
    Allow maxscale startup configuration to be controlled on rpms via /etc/sysconfig/maxscale
  8. New Feature MXS-298
    Please tag in git your release versions and provide better linking to the download locations
  9. Bug MXS-626
    Don't log anything to maxlog until it is known whether that is wanted.
  10. Bug MXS-583
    MaxScale malloc(): memory corruption with wrong router_option
  11. Bug MXS-511
    ReadWriteSplit router won't choose node as master and logs confusing "RUNNING MASTER" error message
  12. New Feature MXS-502
    Log server state changes
  13. Bug MXS-487
    lost connection to backend server
  14. New Feature MXS-448
    Better handling of queries in the binlog router
  15. Bug MXS-443
    Network outages cause highly repetitive error reporting in the logs
  16. Task MXS-439
    MaxInfo Improvements
  17. Sub-Task MXS-438
    Add shutdown/restart commands to maxinfo
  18. Sub-Task MXS-437
    Add flush logs and set/clear server to maxinfo
  19. Bug MXS-436
    Invalid threads argument is ignored and MaxScale starts with one thread
  20. Bug MXS-427
    Logging a large string causes a segmentation fault
  21. Bug MXS-419
    Socket creation failed due 24, Too many open files.
  22. Bug MXS-407
    Maxscale binlogrouter binlog names are unncessarily length-limited
  23. Task MXS-1139
    High load
  24. New Feature MXS-660
    Live events notification to slaves
  25. New Feature MXS-655
    Maxscale log rotation stymies logrotate
  26. Bug MXS-392
    Update to "Rabbit MQ setup and MaxScale Integration" document
  27. Bug MXS-386
    max_sescmd_history should not close connections
  28. Bug MXS-385
    disable_sescmd_history can cause false data to be read.
  29. Task MXS-382
    Regular asserts should not be used in test programs.
  30. Bug MXS-379
    Incorrect handing of a GWBUF may cause SIGABRT.
  31. Bug MXS-374
    Maxscale is running under 'root' in Ubuntu/Debina
  32. Bug MXS-373
    If config file is non-existent, maxscale crashes.
  33. Sub-Task MXS-369
    1.2.1 Technical Documentation
  34. Task MXS-368
    1.2.1 Release Preparations
  35. Bug MXS-365
    Load data local infile connection abort when loading certain files
  36. New Feature MXS-341
    MaxScale won't work on MySQL 5.7 due to missing password column in mysql.user table
  37. New Feature MXS-288
    Error on login for Mysql >= 5.7.6
  38. Bug MXS-281
    SELECT INTO OUTFILE query goes several times to one slave
  39. Bug MXS-274
    Memory Leak
  40. Bug MXS-594
    Binlog name gets trunkated
  41. Bug MXS-587
    readwritesplit module - intensive load - SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query
  42. Bug MXS-586
    Tee filter hangs when using range
  43. Bug MXS-579
    Slave failure not handled gracefully in readwritesplit
  44. Bug MXS-566
    MEDIUMBLOB column update issues
  45. Bug MXS-561
    Maxscale ignores --libdir(-B) startup option
  46. Bug MXS-560
    Server status unknown after reloading config
  47. Bug MXS-548
    Maxscale 1.2.1 crash on Ubuntu 14.04.3 x86_64
  48. New Feature MXS-510
    Wildcards in host names are not supported for authentication
  49. Bug MXS-501
    USE <db> hangs when Tee filter uses matching
  50. Bug MXS-497
    MaxScale does not contemplate client multiple statements (CLIENT_MULTI_STATEMENTS)
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