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-30607
          MongoS logs build info twice at startup
        2. Bug SERVER-42204
          ReplBatcher must handle exceptions from OplogApplier::calculateBatchLimitBytes
        3. Bug SERVER-41989
          BSONObjBuilder::asTempObj is not exception safe
        4. Bug SERVER-42372
          Reads against capped collections aren't banned within transactions
        5. Task SERVER-42000
          Remove blacklist for invalid_system_views_sharded_collection.js after next 4.2 release
        6. Improvement SERVER-42137
          Allow aggregation $merge stage to write to a collection that the query also reads from
        7. Bug SERVER-42251
          Cannot timestamp multikey write during recovery of prepared transaction before LogicalClock has been initialized
        8. Bug SERVER-42219
          Oplog buffer not always empty when primary exits drain mode
        9. Bug SERVER-42171
          Race in recover_prepared_transactions_startup_secondary_application.js
        10. Task SERVER-42021
          Add insert large doc workload to system_perf.yml
        11. Task SERVER-42198
          trafficRecordingDirectory="./" fails
        12. Task SERVER-41931
          Remove forceRollbackViaRefetch flag
        13. Task SERVER-42200
          Update the automated backup restore tests to conform with the published specification
        14. Bug SERVER-42026
          Lock during ConnectionPool::SpecificPool::spawnConnections()
        15. Improvement SERVER-42116
          Update with aggregation pipeline shows in oplog as replace operation
        16. Bug SERVER-42017
          Stage names in error message should match name used
        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