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-4834
    MaxScale should log a warning if failover may lose transactions
  2. Bug MXS-5021
    gdb-stacktrace is incorrectly presented as a debug option
  3. Bug MXS-5085
    max_slave_connections=0 may create slave connections after a switchover
  4. New Feature MXS-5067
    Add "enforce_read_only_servers" feature to MariaDB Monitor
  5. Task MXS-5026
    Documentation refers to MaxScale 7
  6. Bug MXS-5010
    Session commands that are executed early are not validated
  7. Bug MXS-5009
    --basedir is broken
  8. Bug MXS-5095
    Master Stickiness state is not documented
  9. Bug MXS-5090
    ability to setup .secrets file location
  10. Task MXS-5084
    Combine all upgrade documents into one.
  11. Bug MXS-5083
    ssl_version in MaxScale and tls_version in MariaDB behave differently
  12. Bug MXS-5082
    Password encryption format change in 2.5 is not documented very well
  13. Bug MXS-5081
    The values of ssl_version in MaxScale and tls_version in MariaDB accept different values
  14. Bug MXS-5074
    Warning about missing slashes around regular expressions is confusing
  15. Bug MXS-5048
    Problem in hostname matching when using regex (%) for user authentication
  16. Bug MXS-5039
    cooperative_monitoring_locks can leave stale locks on a server if network breaks
  17. Bug MXS-5038
    Maxscale key limitations
  18. Bug MXS-5031
    enforce_read_only_slaves can set master to read_only
  19. Task MXS-5025
    Module maturities are very out of date
  20. Bug MXS-4902
    MariaDB Monitor command reset-replication can be started on a secondary MaxScale
  21. Bug MXS-5014
    During Failover Passive MaxScale route writes to the Old Master
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