Export - CSV (All fields)
Export - CSV (Current fields)
ODATA-829
Section 7.2, Examples 50: aggregate returns one item even for empty input setODATA-759
6.2.3 Custom Aggregates: unprecise formulationODATA-728
A recursive hierarchy annotation may also contain a navigation property to the parent nodeODATA-727
Clarify the meaning of annotation values used for hierarchy termsODATA-726
Describe the data model used for example 75ODATA-725
Missing navigation properties in diagram in section 2.2ODATA-703
Example 31: wrong descriptionODATA-702
Define the behaviour of system query option $count and path segment /$count in combination with $applyODATA-701
Bug in Example 38: terms for LeveledHierarchy and RecursiveHierarchy incorrectly annotatedODATA-662
Allow usage of $apply as "Expand Option" in $expandODATA-588
Typo in example 10: query uses MaxAmount, response uses MinAmountODATA-543
Nullable attribute on collection property should specify whether collection can contain null valuesODATA-542
Clarify that $selected Actions/Functions are included in [project-list] within a ContextUrlODATA-540
Explicitly state that the Context URL locates (a specific portion of) the metadata documentODATA-539
Delta response encoding is unnecessarily verbose and change type is missing when odata.metadata=noneODATA-538
Clarify treatment of odata.type with derived types and odata.context for delta responses for odata.metadata=noneODATA-537
Ordering of navigationLink and associationLink annotations in JSONODATA-536
Treatment of circular references when using $levelsODATA-535
Define specialization for termsODATA-534
Tag type definition in Core should have default boolean value = trueODATA-533
Restrict key property aliases to key properties nested in complex propertiesODATA-532
Clarify whether collections can contain null valuesODATA-531
Simplify OptimisticConcurrency in Core vocabularyODATA-530
Navigable capability term should apply to entityset, not navigationproperty directlyODATA-529
Single-parameter cast() and isof() functionsODATA-528
$entity should require cast segment in order to apply $select/$expandODATA-527
Relative URLs in OData and the ability to put OData services behind an HTTP proxyODATA-526
Allow specifying support for cross-joinsODATA-525
Remove Org.OData.Atom vocabularyODATA-524
properties in [propertyList] of context URL may be qualified with typeODATA-523
How do clients construct links from the context url for complex types?ODATA-522
Clarify that the has operator returns null if either operand is null.ODATA-521
Remove typed null literalsODATA-520
Instance annotations should be prefixed with "@"ODATA-519
Define server-driven paging for collection-valued resourcesODATA-518
Use NavProp@<annotation-name> to reference annotations applied to a NavPropODATA-517
Allow NavigationPropertyPath and PropertyPath expressions to end in annotations of appropriate typeODATA-515
Section 5.1.1.9 Operator Precedence: operators use wrong capitalization in precedence tableODATA-514
Example 44: compare Price to a number instead of a stringODATA-513
Special handling of derived types in the dynamic expression edm:Record. Why?ODATA-512
14.5.14: add example for specifying a value for a navigation property in a <Record> expressionODATA-511
13.6 and 13.6.2: "bound" should hyperlink to section 12.2.3 instead of 12.1.3ODATA-510
Example 78: replace IsBindable with IsBoundODATA-509
14.1: Superfluous period at end of second sentenceODATA-508
Delete leftover "respectively" from 6th paragraph of [JSON] Section 5, Service DocumentODATA-507
Editorial; text appears twice in section 11.2.6 of [Protocol]ODATA-506
Rule day does not allow the values 10 and 20ODATA-505
Remove ReturnType attribute from Action and Function elementODATA-504
Comment in line 456 should refer to rule lambdaVariableExprODATA-503
Error in ABNF grammar: Edm prefix required for built-in primitive typesODATA-502
Fix use of hash (#) for category term attribute in AtomODATA-501
has operator is missing from the operator precedence tableODATA-500
Require function/action overloads to differ by ordered set of parameter typesODATA-499
7.1.3 Nullable should refer to NavigationProperty, not PropertyODATA-498
Error with m:type in Example 31 of AtomODATA-497
Remove type prefix and single quotes for URL literals of types Date, DateTimeOffset, Guid, and TimeOfDayODATA-496
Adapt outdated action/function overload resolution rules in Part 1 to current rules in Part 3ODATA-495
Clarify that Edm.Double and Edm.Single are 64-bit and 32-bit IEEE754 floating-point numbersODATA-493
Capabilities vocabulary: add term for SearchRestrictionsODATA-492
Add example for „has" operator to section 5.1.1.1.10ODATA-491
Language-dependency of key property valuesODATA-490
Clarify Referential Constraints have UpdateRule=Cascade semanticsODATA-489
Clarify wording for OnDeleteODATA-488
Restrict values of edm:Bool in edm.xsd to lower-case "true" and "false"ODATA-487
Clarify where relative URLs follow the rules in section 4.3 and where they follow different rulesODATA-486
Missing <Record> wrapper in three examplesODATA-485
Add example for UrlRef expression that contains a literal string that is a URLODATA-484
Remove reference to "fixed-length or variable-length" primitive valuesODATA-483
Include all section levels in table of contents, provide anchors for all document sectionsODATA-481
Annotation/Navigation/Path expressions: allow paths to continue after multi-valued navigation to e.g. drill into complex propertiesODATA-478
Clarify format for values of Content-ID header in $batch partsODATA-477
Clarify that dynamic properties can be used in all system query optionsODATA-476
Clarify that type-cast segments are required for properties of derived types in system query optionsODATA-475
Document that the value "%" is used for annotating percentages with Measures.UnitODATA-474
Add example for POST/PUT/PATCH/DELETE on function resultODATA-473
Harmonize description of function overload advertisement in Atom and JSONODATA-472
Explicitly state how dynamic properties are represented if they are not defined on an entityODATA-471
Property names must also be a valid XML Names (NCName)ODATA-470
Clarify behavior of /$value requests to properties of type Edm.Binary or Edm.Geo*ODATA-469
Type of Extends attribute in edm.xsd must be TQualifiedName instead of TSimpleIdentifierODATA-468
Define explicit concepts in ABNF for referenced sets of rulesODATA-466
Edm.Binary should be base64-encoded (as with OData V3), not base16-encoded (as per current ABNF)ODATA-9
allow expressions in the $select query option
{"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