Log inSkip to main contentSkip to sidebar
OASIS Technical Committees Issue Tracker
  • Dashboards
    • Projects
      • Issues
        • Status Time Free
        • Give feedback to Atlassian
        • Help
          • Keyboard Shortcuts
          • About Jira
          • Jira Credits
        • Log In

        Export - CSV (All fields)

        Export - CSV (Current fields)

        Comma (,) Semicolon (;) Vertical bar (|) Caret (^)
        1. New Feature ODATA-1463
          Align wording on "safe" and "idempotent" with RFC 7231
        2. New Feature ODATA-1287
          Annotate a property as "cannot be specified on insert, can be updated later"
        3. Sub-task ODATA-1285
          Add ReadByKeyRestrictions similar to ReadRestrictions
        4. Improvement ODATA-1153
          Core.Immutable: clarify that value can be provided *by client* in insert
        5. Bug ODATA-1134
          Add KeyAsSegmentSupported annotation term to Capabilities vocabulary
        6. Improvement ODATA-1124
          Authorization vocabulary: KeyLocation - also allow cookie as value?
        7. Bug ODATA-1122
          Add singletons for capability term targets
        8. Bug ODATA-1120
          Put entity set restrictions on NavigationPropertyDescriptions
        9. Bug ODATA-1119
          Add CollectionPropertyRestrictions capability term
        10. New Feature ODATA-1112
          Default page size for server-driven paging
        11. New Feature ODATA-1099
          Add annotations to describe custom query options and custom headers
        12. Improvement ODATA-1098
          xxxRestrictions can be applied more broadly
        13. New Feature ODATA-1082
          Add term Constraint to Validation vocabulary
        14. Bug ODATA-1079
          Several issues with latest standard vocabularies
        15. New Feature ODATA-1069
          New term Core.OperationAvailable
        16. Improvement ODATA-1055
          DeepInsertSupport: allow applying to entity sets and collection-valued navigation properties
        17. Improvement ODATA-1031
          Define term for links to related information
        18. Improvement ODATA-925
          Define Core term for service/schema/model version
        19. Bug ODATA-914
          Comments from OASIS Technical Advisory Board (TAB)
        20. Bug ODATA-911
          Miscellanous feedback (public comment c201602e00003)
        21. Bug ODATA-910
          Consider format that is tailored for programmatic access (public comment c201602e00002)
        22. New Feature ODATA-907
          Consider Swagger for describing OData metadata in JSON format (public comment c201602e00000)
        23. Bug ODATA-902
          4.5.2: make "annotations" a hash-map with the target as key
        24. Improvement ODATA-890
          Specify how to get from a JSON message to a JSON schema for validating this message
        25. Improvement ODATA-889
          Make edm.json a stand-alone schema
        26. Bug ODATA-872
          Consider defining structure of bound actions/functions
        27. Sub-task ODATA-863
          Represent Terms similar to Types
        28. Improvement ODATA-844
          Provide JSON versions of the Core, Capabilities, Measures, and Aggregation vocabularies
        29. Improvement ODATA-584
          Change the name of the "AllPropertiesSupported" property of the "ApplySupported" term to something more meaningful
        30. Bug ODATA-583
          Clarify intentions around implied ordering of input set to aggregation transformations
        31. Improvement ODATA-582
          Simplify custom aggregate term
        32. Improvement ODATA-581
          Remove parameterless aggregate() transformation
        33. Bug ODATA-577
          Do we need a way to distinguish between properties that are omitted due to being aggregated away versus those that don't apply (i.e., in a concatenated result)?
        34. Improvement ODATA-576
          Aggregation: Can we find a better way to represent nested expands?
        35. Improvement ODATA-575
          Rationalize vocabulary and other editorial changes
        36. Improvement ODATA-574
          Rationalize Aggregatable Properties, Dynamic Aggregates, and floating aggregates
        37. Improvement ODATA-465
          Explicitly mention that complex type instances can have stream properties (public comment c201307e00000)
        38. Bug ODATA-464
          Disallows $format for delta and next links
        39. Bug ODATA-463
          Deleted-entry, link, and deleted-link should include {entity-set} in context URL
        40. Improvement ODATA-460
          Add terms to capability vocabulary
        41. Improvement ODATA-459
          State consequences of using IRIs that are not URLs
        42. Bug ODATA-458
          odata.isolation should be a header rather than an expectation
        43. Bug ODATA-457
          Require hash (#) on odata.type
        44. Bug ODATA-456
          Don't require client to specify odata.trackchanges preference on each page
        45. Improvement ODATA-455
          Make EntityContainer a Singleton in MetadataService
        46. Bug ODATA-454
          Need a way to specify a property is unavailable
        47. Bug ODATA-453
          deal with KEY function
        48. Bug ODATA-452
          Services should be allowed to filter changes based on selected fields
        49. Improvement ODATA-451
          Provide section that clearly indicates what system query options are allowed on the various combinations of URL type and HTTP method (public comment c201306e00012)
        50. Bug ODATA-450
          ordering of association link , navigation link, expanded nav prop
        51. Improvement ODATA-449
          Clarify restrictions for action/function overloads, rename IsBindable to IsBound
        52. Bug ODATA-448
          Add Nullable facet to edm:ReturnType
        53. Improvement ODATA-447
          Rename Metadata URL to Context
        54. Improvement ODATA-446
          Rename Named Stream to Stream Property
        55. Improvement ODATA-445
          odata.type relative to odata.type in surrounding entities
        56. Bug ODATA-444
          Representation of entity references
        57. Bug ODATA-443
          Last page of delta response MUST contain a delta link
        58. Improvement ODATA-442
          Adapt metadata service
        59. Bug ODATA-441
          Specify canonical form of entity-id
        60. Bug ODATA-440
          Specify response for function or action that returns a single null value
        61. Bug ODATA-439
          Complete Context URL patterns
        62. Improvement ODATA-438
          Rename edm:Url to edm:UrlRef
        63. Bug ODATA-437
          Describe path syntax for edm:Annotations/@Target
        64. Bug ODATA-436
          Allow annotating edm:Annotation element, disallow annotating edm:Collection element
        65. Improvement ODATA-435
          Simplify URL syntax and CSDL by restricting services to exactly one entity container
        66. Bug ODATA-434
          Introduce path segment for cross-joins on entity-container level
        67. Bug ODATA-433
          Rollback requirement that services support $expand
        68. Improvement ODATA-431
          Add $expand=*, $expand=*/$ref, $expand=*($levels=...) for expanding all navigation properties
        69. Improvement ODATA-430
          Add term Core.ResourcePath to describe unconventional resource paths in CSDL
        70. Bug ODATA-429
          Add Boolean property RequiresFilter to Capabilities.FilterRestrictionsType
        71. Bug ODATA-428
          Introduce dynamic expression AnnotationPath and accompanying abstract type Edm.AnnotationPath
        72. Bug ODATA-427
          Consider Providing More Information For Changed Links In a Delta Response
        73. Bug ODATA-426
          Metadata URL for nested objects can be relative to metadata URL of enclosing object
        74. Bug ODATA-425
          Clarify rules around parameter overloads and return types
        75. Improvement ODATA-423
          Rename edm:Entity to edm:Singleton
        76. Improvement ODATA-422
          Add metadata URL to representations of entity references, define format for collections of references
        77. Improvement ODATA-421
          Remove odata.kind from JSON and add metadata URL templates for link, deletedLink, and deletedEntity
        78. Bug ODATA-420
          Response codes 404 and 405: MUST instead of SHOULD
        79. Bug ODATA-419
          Specify ETag handling more precisely
        80. Bug ODATA-418
          EntitySet attribute or NavigationPropertyBinding child elements for Named Entities (edm:Entity)
        81. Bug ODATA-417
          Define content negotiation and default format for paths ending in /$value, /$count, /$metadata and /$batch
        82. Bug ODATA-415
          Use of "MUST," "MAY," "SHOULD," etc in Part 3 CSDL definitions
        83. Bug ODATA-414
          Fix syntax for deleting links to support containment
        84. Bug ODATA-413
          Replace conformance clauses in URL and CSDL with references to Protocol
        85. Improvement ODATA-412
          Consistent representation of empty values
        86. Improvement ODATA-411
          Reconsider placement and semantics of OnDelete element
        87. Improvement ODATA-410
          Consider moving terms OptimisticConcurrencyControl and AcceptableMediaTypes from Core to Capabilities
        88. Bug ODATA-409
          11.3.3.1 conflicts with conformance for intermediate and advanced OData
        89. Bug ODATA-408
          11.2.3 OData services MAY/SHOULD/MUST expose their data model
        90. Improvement ODATA-407
          Navigation Properties in Complex Types (public comment c201305e00012)
        91. Improvement ODATA-406
          Attribute ContainsTarget (public comment c201305e00009)
        92. Improvement ODATA-404
          Make Capabilities vocabulary a part of OData 4.0
        93. New Feature ODATA-403
          Mechanism to advertise conformance level of OData services
        94. Improvement ODATA-402
          Require services to support $expand on navigation properties
        95. Improvement ODATA-401
          Replace "substringof" canonical function with "contains"
        96. Improvement ODATA-400
          Allow JSON values also in common expressions, not only in parameter aliases
        97. Improvement ODATA-399
          Describe expected life cycle management of next-links inside 11.2.4.7 Server-Driven Paging
        98. Improvement ODATA-398
          Define canonical function as a path segment that allows retrieving an entity by its id
        99. Improvement ODATA-397
          Lazy loading of Annotations: Add optional Attribute "TargetNamespace" to edmx:IncludeAnnotations element
        100. Bug ODATA-396
          Partner attribute of edm:NavigationProperty is a property path, not a SimpleIdentifier
        101. Improvement ODATA-395
          Simplify rule for implicit values of enumeration members
        102. Sub-task ODATA-394
          Introduce path segment /$all for search on service and entity container level
        103. Sub-task ODATA-393
          Allow querying collections of primitive type instances similar to other collections
        104. Improvement ODATA-392
          Expanded Navigation Properties should be implicitly added to $select
        105. Improvement ODATA-391
          Add query function isdefined(PropertyPath) to determine whether an instance has a property of that name
        106. Bug ODATA-390
          Additional description of use of GeoJSON in OData JSON.
        107. Bug ODATA-389
          JSON: use odata.kind values "Entity" and "deletedEntity", Atom: use metadata:link and metadata:deleted-link
        108. Bug ODATA-388
          Remove "when" from OData-specific items in delta responses
        109. Improvement ODATA-387
          Replace (at least) the second example in Section 13 of the CSDL document (public comment c201305e00002)
        110. Improvement ODATA-386
          odata-v4.0-csprd01-part1-protocol, 3 Data Model, appears to be an unnumbered list of definitions, with annotations defined in a separate subsection - suggest new format, etc.
        111. Improvement ODATA-385
          Overview wording suggestion
        112. Bug ODATA-384
          Normative text needs to be typographically distinct from examples
        113. Bug ODATA-383
          Number all examples in all documents
        114. Bug ODATA-382
          Conformance clauses need to refer to sections defining aspects of conformance and do so uniformly
        115. Bug ODATA-381
          Hanging paragraphs - all current csprd01 documents
        116. Improvement ODATA-380
          Insert a section in protocol (and similar in JSON and ATOM) named 'Security Considerations' (before 'Conformance')
        117. Improvement ODATA-379
          Ensure consistency and clear description in specification of $count for 'Delta Responses' (public comment c201305e00000)
        118. Bug ODATA-378
          Support relative IRIs for ids in JSON
        119. Bug ODATA-377
          Fix broken links in CSD01 documents
        120. Bug ODATA-376
          Navigation link representation for navigation properties of complex type instances
        121. Improvement ODATA-375
          Allow querying collections of complex type instances similar to querying collections of entities
        122. New Feature ODATA-374
          Returning heterogeneous types for a function call
        123. Improvement ODATA-373
          Add boolean expressions that can be used in <edm:If>
        124. Improvement ODATA-371
          Clearly describe behavior of PUT for structural and navigation properties
        125. Bug ODATA-370
          Disallow Nullable facet for collection-valued properties
        126. Bug ODATA-369
          POST to navigation link with binding information leading to a different "parent" is invalid
        127. Bug ODATA-368
          Deep insert: if server responds with 201 Created it MUST respond with at least the expansion depth of the insert operation
        128. Bug ODATA-367
          Explicitly state that server MAY expand results beyond what's requested with $expand
        129. Improvement ODATA-366
          Clarify whether server-generated properties can be omitted in POST, even if they are not nullable
        130. Improvement ODATA-365
          Rename edm:AssertType to edm:Cast and clarify behavior of edm:Cast and cast()
        131. Improvement ODATA-364
          Explicitly state that the restriction that a property MUST NOT have the same name as its containing type only applies to directly declared properties
        132. Improvement ODATA-351
          Define ID, ReadLink and EditLink in Part 1: Protocol, define representation in Atom and JSON
        133. Improvement ODATA-346
          Order of child elements of <edm:Collection> MUST be preserved
        134. Improvement ODATA-317
          Allow multiple reads in the same transaction
        135. Improvement ODATA-301
          Guidance around data authorization model and secure authenticated access to an OData Service
        136. New Feature ODATA-295
          Services should be able to "advertise" what form of change tracking they support
        137. Improvement ODATA-294
          Clarifications needed for Filter System Query Option: Operators and Functions
        138. Improvement ODATA-289
          Callback for notification after async invocation of Create, Update, Delete and Service Operations
        139. New Feature ODATA-165
          Support Cross-joins
        140. Improvement ODATA-152
          JSON: Add examples for all request and response types using a consistent sample OData service
        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 community license for OASIS. Try Jira - bug tracking software for your team.

        Atlassian