Log inSkip to main contentSkip to sidebar
MongoDB Jira
  • Dashboards
    • Projects
      • Issues
        • eazyBI
        • Give feedback to Atlassian
        • Help
          • Keyboard Shortcuts
          • About Jira
          • Jira Credits
        • Log In
          • Acknowledged notifications

        Export - CSV (All fields)

        Export - CSV (Current fields)

        Comma (,) Semicolon (;) Vertical bar (|) Caret (^)
        1. Bug SERVER-46056
          [WTCheckpointThread] Got signal: 6 (Aborted)
        2. Bug SERVER-44675
          server_status_metrics.js fails due to racy repl.buffer.count metric in serverStatus
        3. Bug SERVER-45935
          [3.6] WT error handler incorrectly prints "An unsupported journal format detected"
        4. Bug SERVER-43109
          Explicitly state nodes in awaitReplication in do_not_advance_commit_point_beyond_last_applied_term.js
        5. Bug SERVER-50891
          mongod 3.6.20-rc2 core dumps if dbpath DNE or perms block
        6. Bug SERVER-43349
          Incorrect serialization for $elemMatch $not $ne
        7. Bug SERVER-44527
          Map reduce to an existing sharded collection can incorrectly create new collections on target shards
        8. Bug SERVER-44477
          Map reduce with mode "merge" to an existing sharded collection may drop and recreate the target if no docs exist on the primary shard
        9. Bug SERVER-44598
          Shards do not treat the IGNORED version as "intended sharded"
        10. Bug SERVER-44834
          mongod block some time, dirty is very high, and do not evit data to disk, io is 0%, my disk is nvme-SSD(this disk io performance is very good)
        11. Question SERVER-44819
          Slow remove on large dataset
        12. Bug SERVER-44273
          Failure to parse certain time zone specifications on windows platforms.
        13. Bug SERVER-44571
          Documents involved in SERVER-44050 corruption scenario cannot be updated or deleted after upgrade
        14. Bug SERVER-44584
          (3.6) Rewriting updates as modifications incorrectly considers logging state
        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 MongoDB. Try Jira - bug tracking software for your team.

        Atlassian