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. Improvement SERVER-28569
          Shell APIs violate ECMAScript's object property order spec
        2. Bug SERVER-31314
          Update os name in macos release tarballs
        3. Bug SERVER-28523
          add warning to group shell helper
        4. Bug SERVER-28812
          Invariant failure when specifying readConcern "majority" and "afterClusterTime" on standalone mongod
        5. Task SERVER-28726
          make ClusterCountCmd::explain, Strategy::explainFind, and DistinctCmd::explain use the ARS
        6. Task SERVER-28656
          consolidate utility functions for forwarding commands to shards into cluster_commands_common.h
        7. Bug SERVER-28698
          Use the 'chunkDataCommitted' failpoint for migration_critical_section_concurrency.js
        8. Task SERVER-28672
          ASIO connection pool rate limiting
        9. Task SERVER-28683
          make ClusterPlanCacheCmd use the ARS
        10. Task SERVER-28628
          Get rid of ParallelSortClusteredCursor
        11. Task SERVER-28641
          remove requirement that non-internal writes against config servers must use writeConcern 'majority'
        12. Task SERVER-28623
          Change TimeProofService::getProof/checkProof to include keyId
        13. Task SERVER-28796
          remove check in CollectionShardingState::onDropCollection that prevents 'config.version' from being dropped
        14. Bug SERVER-28792
          make dropIndexes unversioned again
        15. Task SERVER-28625
          replace ClusterAggregate's use of Strategy::commandOp/ShardConnection with establishCursors/Shard::runCommand
        16. Bug SERVER-28353
          make ARS actually interruptible from the deadline on the OperationContext
        17. Bug SERVER-29348
          Range deletion write majority failure not propagated
        18. Bug SERVER-29191
          Dropping an index named "*" is ambiguous because createIndexes permits an index to be named "*"
        19. Bug SERVER-28689
          fix bug in drop_sharded_dbs.js where we assert.neq() on an entire array and its member
        20. Improvement SERVER-28670
          Add sharding metadata refresh metrics section to serverStatus
        21. Task SERVER-28682
          make ClusterIndexFilterCmd and ClusterPlanCacheCmd use the ARS
        22. Task SERVER-28685
          make mongos's FileMD5Cmd use TaskExecutor::scheduleRemoteCommand
        23. Task SERVER-28684
          Make mongos's version of the 'validate' and 'eval' commands use the ARS
        24. Task SERVER-28681
          make ClusterCountCmd::run use the ARS
        25. Task SERVER-28661
          make gatherResults() return vector<AsyncRequestsSender::Response> instead of vector<ShardAndReply>
        26. Improvement SERVER-28542
          make ARS store interrupt status instead of CallbackCanceled in remotes if interrupted
        27. Bug SERVER-28739
          make the js scripting engine correctly verify that accessed collections are unsharded
        28. Bug SERVER-28746
          eval can deadlock on mmap flush lock when waiting for writeConcern
        29. Task SERVER-28605
          Implement KeysCollectionDocument
        30. Bug SERVER-28697
          Ignore some NoProgressMade errors in sharding_balance4.js
        31. Task SERVER-28627
          replace MapReduceFinishCommand's use of ParallelSortClusteredCursor with establishCursors()/ARM
        32. Task SERVER-28591
          rename ShardingTaskExecutor to ShardTaskExecutor
        33. Task SERVER-28562
          Move LogicalTime HMAC computation outside collection lock
        34. Bug SERVER-30339
          Enabling profiling and read concern majority with a workload of reads and no writes causes accumulation of dirty data
        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