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-5005
    SQL_MODE=ORACLE assignment doesn't recognize autocommit=0
  2. Bug MXS-4930
    'maxctrl reload tls' has the usage of 'maxctrl reload service'
  3. Bug MXS-5007
    Top-level service reconnection may cause a use-after-free
  4. Bug MXS-4967
    Log throttling is sometimes disabled too early
  5. Bug MXS-4954
    Don't send errors if client has already sent a COM_QUIT
  6. Bug MXS-4952
    Doubled quotes inside quoted strings do not collapse correctly when canonicalizing query strings
  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-5023
    kill user and transaction_replay don't play well together in Galera cluster
  10. Bug MXS-4906
    MonitorWorker::call_run_one_tick() called more often than intended
  11. Bug MXS-5206
    Readwritesplit does not drop connections to severely lagging servers
  12. New Feature MXS-4946
    Use relative paths in MaxGUI
  13. Bug MXS-5010
    Session commands that are executed early are not validated
  14. Bug MXS-4998
    MaxScale may send two COM_QUIT packets
  15. Bug MXS-4996
    Order of servers is different after restart if runtime modifications have been done
  16. Bug MXS-4995
    The "static" property of an object is lost upon restart
  17. Bug MXS-4994
    Multiple warnings from the REST-API are printed on the same line
  18. Bug MXS-4992
    Documentation Link in GUI leads to 404 page not found
  19. New Feature MXS-4991
    autoregister oidc user
  20. Bug MXS-4988
    maxscale doesn't properly close connections for TCP health check probes
  21. Bug MXS-4985
    Master loses master status when slaves are shut down
  22. Bug MXS-4983
    Schemarouter monitoring requirements are not documented clearly
  23. Bug MXS-4980
    show shards does not show all information expected
  24. New Feature MXS-4977
    Schemarouter opens a connection to all shards
  25. Bug MXS-4970
    SET GLOBAL should not be stored in the session command history
  26. Bug MXS-4969
    Can't create more than max_prepared_stmt_count statements
  27. Bug MXS-4968
    REST-API TLS certificates can be reloaded but the path to them cannot be altered
  28. Bug MXS-4966
    mariadb-dump gets an error dumping schemas
  29. Bug MXS-4965
    auth_all_servers should be enabled automatically
  30. Bug MXS-4964
    Simple sharding tutorial is out of date
  31. Bug MXS-4963
    Docu for SchemaRouter Simple Sharding does not work
  32. Bug MXS-4961
    Result of KILL CONNECTION_ID() does not propagate all the way to the client
  33. Bug MXS-4959
    COM_STMT_EXECUTE is not logged by qlafilter
  34. Bug MXS-4955
    Character set 'utf8mb3' is not supported
  35. Bug MXS-4953
    Lost connection to backend server: Network error: 104, Connection reset by peer
  36. Bug MXS-4948
    Unable to see columns of view in the Query Editor
  37. Bug MXS-4945
    GUI doesn't validate object name uniqueness accurately
  38. Bug MXS-4944
    Logically identical runtime configurations are not erased
  39. Bug MXS-4943
    delayed_retry timeout errors do not have enough information
  40. Bug MXS-4934
    Use-after-free after service deletion
  41. Bug MXS-4926
    History length of sessions is not visible in the REST-API
  42. Bug MXS-4925
    self link in /maxscale/logs/data is off by one page
  43. Bug MXS-4918
    Readconnroute router allows starting a transaction which stops replication on slave due to 'Lock wait timeout exceeded; try restarting transaction' error
  44. Bug MXS-4914
    GUI dashboard's width is reduced unexpectedly
  45. Bug MXS-4900
    maxctrl show qc_cache can easily overwhelm MaxScale
  46. Bug MXS-4893
    Query history retention period increases unexpectedly every time the setting dialog is opened
  47. Bug MXS-4891
    Query editor schema explorer is disabled after reconnecting connections
  48. Bug MXS-4888
    Unable to type custom row limit in the Query configuration dialog
  49. Bug MXS-5027
    Duplicate shard detection cannot be turned off
  50. Bug MXS-4879
    Transaction state viewed from the session is different from the transaction state as viewed from RWS.
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