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-4930
    'maxctrl reload tls' has the usage of 'maxctrl reload service'
  2. Bug MXS-5008
    Log message on releasing exclusive locks when no lock majority is confusing
  3. Bug MXS-5007
    Top-level service reconnection may cause a use-after-free
  4. Bug MXS-4997
    MaxScale: BUILD/install_build_deps.sh: deprecated --force-yes
  5. Bug MXS-4979
    COM_CHANGE_USER may leave stale IDs to be checked
  6. Bug MXS-4967
    Log throttling is sometimes disabled too early
  7. Bug MXS-4935
    False protocol incompatibility error
  8. Bug MXS-4924
    Very fast client and server may end up busy-looping a worker
  9. Bug MXS-4906
    MonitorWorker::call_run_one_tick() called more often than intended
  10. Task MXS-5011
    Upgrade libssh to 0.10.6
  11. Bug MXS-4998
    MaxScale may send two COM_QUIT packets
  12. Bug MXS-4996
    Order of servers is different after restart if runtime modifications have been done
  13. Bug MXS-4995
    The "static" property of an object is lost upon restart
  14. Bug MXS-4994
    Multiple warnings from the REST-API are printed on the same line
  15. Bug MXS-4992
    Documentation Link in GUI leads to 404 page not found
  16. Bug MXS-4988
    maxscale doesn't properly close connections for TCP health check probes
  17. Bug MXS-4981
    Hang on shutdown when large batches of session command are pending
  18. Bug MXS-4980
    show shards does not show all information expected
  19. Bug MXS-4978
    Read-only transactions are incorrectly tracked
  20. Bug MXS-4969
    Can't create more than max_prepared_stmt_count statements
  21. Bug MXS-4968
    REST-API TLS certificates can be reloaded but the path to them cannot be altered
  22. Bug MXS-4961
    Result of KILL CONNECTION_ID() does not propagate all the way to the client
  23. Bug MXS-4956
    Session commands ignore delayed_retry_timeout
  24. Bug MXS-4948
    Unable to see columns of view in the Query Editor
  25. Bug MXS-4947
    Tables in information_schema are treated as a normal tables
  26. Bug MXS-4945
    GUI doesn't validate object name uniqueness accurately
  27. Bug MXS-4943
    delayed_retry timeout errors do not have enough information
  28. Bug MXS-4934
    Use-after-free after service deletion
  29. Bug MXS-4926
    History length of sessions is not visible in the REST-API
  30. Bug MXS-4925
    self link in /maxscale/logs/data is off by one page
  31. Bug MXS-4914
    GUI dashboard's width is reduced unexpectedly
  32. Bug MXS-4912
    Query classifier cache total-size book-keeping may be wrong
  33. Bug MXS-4900
    maxctrl show qc_cache can easily overwhelm MaxScale
  34. Bug MXS-4898
    MaxScale sends wrong character set (session tracking)
  35. Bug MXS-4896
    Reducing the size of the query classifier cache does not cause excess entries to be freed.
  36. Bug MXS-4893
    Query history retention period increases unexpectedly every time the setting dialog is opened
  37. Bug MXS-4891
    Query editor schema explorer is disabled after reconnecting connections
  38. Bug MXS-4888
    Unable to type custom row limit in the Query configuration dialog
  39. Task MXS-4882
    ODBC libraries not included in package
  40. Bug MXS-4879
    Transaction state viewed from the session is different from the transaction state as viewed from RWS.
  41. Bug MXS-4910
    readconnroute performance regression in 6.4
  42. Task MXS-4909
    Use different data dirs for diffarent MariaDB versions
  43. Bug MXS-4907
    Nested parameters in PATCH /v1/maxscale/ do not work correctly
  44. Task MXS-4905
    Warn about THP after startup
  45. Task MXS-4904
    Report entry size in "maxctrl show qc_cache"
  46. Bug MXS-4903
    Bad configuration in PATCH may partially configure monitors
  47. Bug MXS-4901
    Turning on log_info causes parsing related errors and warnings
  48. Bug MXS-4865
    5.5.5- prefix should not be added if all backends are MariaDB 11
  49. Task MXS-4832
    Add a way to detect that a client connected to MaxScale
  50. Bug MXS-4982
    OpenSSL system call error is logged as ERROR when client disconnects abruptly
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