Export - CSV (All fields)
Export - CSV (Current fields)
WSCALENDAR-562
Duration text in Tale 3-4 is incorrectWSCALENDAR-556
Reference to Web Links is incorrect
Description of Granularity and Tolerance is inconsistent and confusing
WS-Calendar generally uses lowerCamel for names. Use it consistently
Granularity is mis-defined in spec as part of ToleranceWSCALENDAR-458
Small change to TZID
Ominbus Issue for Sharon Dinges comments
Name is "Mike Douglass" not "Mike Douglas"
General Approach to Normative References
Appendix
Section 4 - RESTful services
Section 5 - Conformance and Rules
All - Does the standard assuming any type of industry? Specification of interoperability for the energy industry is lacking. Certain assumptions will leave the interoperability more difficult and costly, rather than generic.
All - implementation Model - Where is the detail?
Section 7.1.3 - This version of standards is not ready for any type adoption or implementation due to lack of Access control, provisioning, retrivals, insertions, deletion, GET and allocation or clarification of services.
All - The use of web services has been assumed or mandated where not all other standards that use ws_calendar have the same assumption or mandate.
All - Security is not addressed anywhere in the standard. It is not sufficient to rely on transport for trust. That would mean mandating the transport mechanism.
Section 3.3.3 - Inheritance rules for Gluons - An information model would be much clearer.
Section 3.3.1.1 - Gluons are another example of a multi-purpose, you don't need it unless it's present class in this standard. It lacks a specific purpose therefore it was very hard to name.
Section 3.1.1 - Choosing one format would benefit interoperability.
Section 3.1 - Schedule is not defined in Table 1.6
Section 3.1.4.1 - Not creating a new type for an "anchored sequence" makes validation very difficult.
Section 3.1.4.1 - Is there some way to define a sequence and then re-use it in several "anchored sequences"
Section 3.1.2 - "An Unscheduled Interval " - Are these terms consistent/overlapping with table 1.6
All - Where is the information model (class model)? The widespread use of inheritance would have been better understood with an inheritance model.
Section 2.3 - "the specification is not prescriptive " - Flexibility will not help with interoperability. A customer has no idea if a vendor that supports this standard which actually interoperate in content or technology.
Section 2.2.1 - "no representation as whether UTC or local time are more appropriate " - A hard decision here would have provided lots of benefit to interoperability. Flexibility will not help with interoperability.
Section 2.2 - ", the service scheduled to shed load " - How does this example change this spec?
Section 2.1 - Most of the vocabulary is specific to this standard not iCal
All - The standard provides every possible method to define intervals and schedules while this is clever it does not increase the chance of interoperability.
Table 1.6 - What values? (Calendar date?)
Table 1.6 - The definition relate to implementation e.g. "need inheritance" or "not complete" rather than the information that is undefined in this state
Table 1.6 - Circular definitions.
Table 1.6 - "An interval is anchored if it is bound..." - Is anchored a synonym for bound
Abstract - If there is nothing energy sector specific in this standard what benefit does it provide over the other standards mentioned.
All - security is not addressed in any way
All - the use of generic data types make it impossible to determine the actual intent of the message and limits validation. An error would change the intent of the message with no way of knowing that an error had occurred
All - the standard does not effectively address the time period definitions that are particular to the wholesale energy markets
Update references in Appendix B to use the normal References style...
Line 2678 - "Intervals SHALL NOT include an END time."
Line 2688 - Section 5.3 "still to come". Missing section in standard document.
iCalendar-wscal-extensions - Gluons and Intervals are recursive
iCalendar-valtypes.xsd
Lines 902, 1026 - Example composition
iCalendar-valtypes.xsd and others.
Line 2676 - Actionable services require Bound Intervals as part of a Bound Sequence. Services may Intervalsarenot bound for informational or negotiation purposes.Some of these are modeled an constraints in the UML models that have been produced separately
Line 143 - Namespaces used in this specification
Line 311 - Parameters are not discussed
Third Collector for purely mechanical edits
On 1322, you usually write "start date and time". On 1323 "start-times" is hyphenated, but not elsewhere
Line 1321 - Why is "Service Advertisements" in the heading? This is more than just "service adv" - should this be "describing" or "managing" "start times"?
Line 370 - This sentence conflates WS-Calendar, iCalendar, xCal, AND talks about a WS-Calendar MESSAGE. This is an INFORMATION MODEL. Fix this sentence.
Line 369 - "Linked to a specific date and time" should be "Bound to a specific [date and] time" The word "tied" could be used, but you've already defined Bound
Line 362 - An Interval is NOT a "unit of service delivery." It's a span of time. The description of "bound to time" should reference "Bound" in table 1-6, and should reference those Semantics Decribing Intervals"
Line 354-356 - The final sentence is incomprehensible as written. And it uses "time segment" which was capitalized in the first sentence. And how are "terms about time" contained "within a particular time segment"?!
Line 354-356 - Change "are a critical component of service alignment using WS-Calendar" to "are a critical way to describe service coordination."
Line 354-356 - We have Intervals, now we have Time Segments? I don't find a definition, and it seems very similar.
Line 344 - This discussion is weakened by the lack of either italics or quotation marks around the strings such as "1M"
All: Ensure that defined or called out terms (e.g. Duration, Schedule, ...) are uniformly capitalized and that non-defined terms are not.
Line 343 - "granularity" is not title case; capitalize.
Line 303 - "Duration" was defined on line 180, and should be capitalized. "schedule" is not defined and should be (and might be as "Schedules" on line 1020). "time" is not defined and probably shouldn't be.
Line 253 "start at a particular instant of time UTC" does not read well. Where is a definition of the acronym UTC? Starting with what is UTC (a single sentence) would make the rest of this section more clear. Is there a normative ref or informative ref?
line 234 - Footnote 6 should have an informative reference [SOA-RM] rather than the "...found in the normative references..." wording. Add [SOA-RM] reference on line 227.
Line 223 - The section title again may lead to confusion between whether this is an information model or a service definition. it is the former; and time semantics are not critical to JUST WS-Calendar. reconsider the focus and message of this paragraph
Line 205 - Compare this first paragraph with e.g. line 43 which talks about what the intent was; this paragraph is in better voice describing how the work was produced.
Line 180 - For Gluon add in definition a footnote "Sometimes referred to as a Calendar Gluon". Or correct use of "Calendar Gluon" in the rest of the document to "Gluon" [preferred].
Line 180 - There is no normative reference to which [XCAL] is connected. Perhaps "xCAL Draft" is what's meant?
Line 180 - Capitalization is variable, look at VTODO and vtodo in the first two lines.
Line 147 - Replace "An ancillary..." with "An additional..." or "Another...". (mild preference)
Line 124 - I believe that this should be [NAESB_PAP04] and reference both the first and second release.
Line 119 - The reference should be something like [NIST Framework] - the title has been turned into a reference shorthand by bolding it. Other places this happened is on lines 59, 105 (should be [xCal Draft]), 119, 124, 131,, and maybe 136.
Line 105 - Is the "Draft xCal" superseded by the contributions and the work in the schemas that are part of this work product? Reword.
Line 59 - Is Calendar Resource Schema truly a normative reference? Where is it cited or used?
Line 49 - delete "(WS-Calendar)"
Lines 43-48: the intent matters less that what is produced in the document in our hands.
Line 34 - there is no reference for [EITC] and [EMIX]; these should be non-normative references. Likewise EDXL and oBIX on lines 35-36
DP-WS has a hyphen on line 24 and not on line 64
Line 93 - Can you have a normative reference to a non-normative document? Date also seems off.
Why are there normative references to WS-Management, WS-Security, DP-WS, XRD, and others including e.g. lines 71, 74, and more? If there is no use of something in a document it seems strange to label it a normative reference.
Cover and starting on line 59: The RFCs listed seem to be out of sync (in the normative references. Verify that current dates are used; Vavailability has been recently updated.
Line 13 - "agent" has many meanings. Perhaps "actor" would be a better choice? Agency is not what's suggested here.
Sentence starting line 4: "Agreement on when something should or did occur is fundamental to negotiating service use."
Lines 1-2 - The emphasis on Web services seems strange; consider "The information model of WS-Calendar is intended to be used to define information payloads for Web services and Service-style interactions [SOA-RM]."
Footnote 3 page 9 - Is OPC UA a trademark? If not, why is it footnoted?
Footnote 2 and 4 page 9 Footnote is repeated. Note that only the first use a a registered trademark could or should be footnoted.
Section 1 line 2 and the rest of the specification: Change "Semantic Model" to "information model" throughout the document
Line 1646 - "Xs:bool" differs how from "xs:bool" and how do they relate to the W3 XML Schema type "boolean"? Fix
Line 1646 - The discussion of "components" at "the realm border" and "overwrite without notice" seems out of place in an information model.
Line 1646 - Should "shall" be "SHALL" in the definition?
Line 1646 - timeStampRealm - do you really mean "A set of points ..."? A set of timestamps? A set of locations?
Line 1020 - Why is "Schedules" plural? You use "schedule" in other places. Is this the name of the attribute? Rather it's the description of a collection of attributes/elements.
Line 898 - Typographically distinguish e.g. 15M, 30M, etc, as suggested elsewhere. If these are strings, put in italic or bold, but be consistent through the document.
Line 869 - Granularity is also on line 718; needs to be related and explain why different (if it is)
Line 887 - why is "availability" different from "vavailability"?
Line 887 - Uid, Summary, dtStart, dtEnd, duration, and Granularity
Line 887 - The relationship of tables 3-7 and 3-8 is not clear.
Line 877 - Vavailability is a 3 year old proposal; there's an update, but are you defining what it is in this document?
Line 881 - The "optionality" of dtEnd and duration is not clearly defined
Line 881 - "use" of "Summary" is not "text" - that's its type. The "Discussion" belongs in use. or change the column heading "Use" to "Type" (but stay consistent with other tables).
Line 858 - WsCalendar Attach the use is "WSCalendar:Attachment" this is very unclear. "The Attach element contains..." and change "incorporating specifications" to "conforming specifications" [ref to section 5.4]
Line 858 - "Designated Interval" text should reference line 196
Line 858 - dtEnd says "SCHEDULED completion time..." is this implied or computed or expressed? dtStart simply says "Start time"
Line 858 - dtEnd is not listed and optional, as are dtStart and duration (DtStart and Duration?)
Line 718 - Capitalization of first column is not consistent with other tables
Line 718 - Reference to "service" seems out of place; consider "operation" as an alternative. On line 712, "service coordination between systems' really should read "action coordination between/across systems" I think.
Line 464 - The relationship may not be determinable if the reltype is inherited along with duration and dtstart until the sequence is Bound.
Line 462 - Reference table 1-3 where "Sequence" is defined.
Line 395 - The capitalization seems almost random across the tables
Line 368 - Elsewhere it's recommended that intervals have DtStart and Duration (either of which can be filled in through eg inheritance), but we see later an odd blend (line 858 adds DtEnd to the mix). This needs to be clear and consistent across the doc.
Line 368 - Why is "attach" not capitalized? that doesn't fit the style of some tables (but see Table 3-2) "attach" mixes "attach" and "Attach". Are they different? Is case important in these tables and the schemas? XML is case sensitive, and this confuses
Line 368 - Both DtStart and Duration are "optional". What precisely does that mean? That neither need to be present? we find later that these values can be inherited from a gluon, but at this point "optional" seems to mean "no value is required"
Section 3 - Table headings change and confuse
Table 3-4 is Attachment Element/Use/Discussion, and the discussion for Text seems out of place.
Table 3-3 ? there IS NO TABLE 3-3.
Table 3-2 is Temporal Relationship/Short Form/ Definitioin/Example - is this because these are DEFINED in WS-Calendar rather than USED?
Table 3-1 headings are Elements/Use/Use in WS-Calendar. Isn't this the WS-Calendar draft standard?
Is there a standard vlue for durations of Month and Year?
Collector for Reference Checks
Collector for Conformance and Data Intetgrity
Line 2936 - replace "prodUTCion" with "production"
Line 2821 - replace the word "Whilst" with the word "While"
Line 2694 - insert an "L" at the end of "SHAL"
Line 2677 & 2678 - insert periods at the end of the sentences
Line 2675 - insert a space between "are" and "not"
Line 2674 - insert the word "have" between "may" and "Intervals"
Line 2635 - insert a period at the end of the sentence
Line 2625 - delete the period
Line 2622 - delete the period
Line 1873-1874 - the use of the word "owner" may be interpreted to apply to certain data, then a term other than "owner" should be used to avoid the legal implications associated with using the term "owner"
Table 3-8 - Punctuation errors
Table 3-7 - punctuation errors
Line 862 - delete the word "and" after the phrase "based on"
Table 3-6 - delete the extra period after "3.2." in the Discussion for "WsCalendar Attach"
Table 3-6 - replace the comma at the end of the Discussion for "duration" with a period
Table 3-6 - delete the periods after "DateTime" and after the word "Interval" in the Use for "dtEnd"
Line 837 - delete "[reference]" and insert the appropriate reference
Table 3-5 - insert the phrase "It may be 0." at the end of the definitions of "startAfterTolerance", "endBeforeTolerance" and "endAfterTolerance"
Line 528 - delete the phrase "one hour," and replace "three" with "3"
Line 454 - insert a period at the end of the sentence
Line 371 - insert a colon after "Interval"
Page 16, Table 1-6 - insert a period at the end of the definition for "Constrained"
Page 15, Table 1-5 - insert a period at the end on the definition for (i) "Bequeath" and (ii) "Inherit"
Page 14, Table 1-4 - grammatic errors
Page 9, Line 7 - insert a dash between "lead" and "times"
PR02 What are you defining? XCAL? WS-Calendar? Some combination?
Collector for Mechanically Editorial Issues
Page 73 - remove spurious footnote
Line 2618 - delete "Semantic" from section header
Line 1662-1663 - change "...in such a way." to "...in this manner."
Line 1655 - "time-stamp" - remove hyphen, use space
Line 1646 - "accuracy" has an unmatched opening parenthesis mark. - add closing parethesis
Line 1644 - "time-stamp" - remove hyphen, use space
Line 1642-1644 - "It is not...that it caused."
Line 1640 - strike "in smart grids"
Line 1324 - "it's" to "its" (remove apostrophe)
Line 1323 - "start-times" - remove hyphen, use space
Line 881 - a comma, not a period, following "...but not both," - change to period
Line 881 - two periods following "...unavailable.."
Line 847 - "...are used to referencing and bind the..." - change "referencing" to "reference"
Line 371 - missing period at end of sentence
Line 368, 858 - inconsistent italicization of "Mandatory" and "Optional" in these and other tables where the terms are employed
Line 332 - redundant reference - delete sentence and put "[ISO8601]" in line 317 as a replacement for "ISO 8601"
Line 263, 266 - use of personal pronoun "you" - reword sentences to eliminate personal pronoun use.
Line 198 - footnote 6 wording - change to "...are as defined in [SOA-RM]."
Line 186 - citation in Table 1-4 for RFC5545 does not follow the OASIS convention - change to [RFC5545]
Line 1646 - the "Note" for "accuracy" uses the abbreviation "resp." without defining it anywhere in the document.
Line 1646 - The "Note" for "timestamp" states "May include two objects as defined above." What two objects? Where above? The "Definition" is "WS-Calendar:time".
Line 870 - the defintion of "Bound" in Table 1-6 does not include Duration, as in "Bound Duration" employed in the sentence.
Line 858 - it is unclear why there is a restriction on using only dtStart and duration, and dtEnd and duration, but NOT dtStart and dtEnd.
Line 718 - Change first column heading to "Parameter"
Line 718 - Change Table heading to "Tolerance Parameters"
Line 706 - heading is unclear and more explicit reference to Tolerance would be appreciated
Line 531-532, 606 - line 606 appears superfluous with lines 531-532.
Line 453-465 - it appears that this language would be better served if the heading 3.1.4 appeared before the text that starts on line 453.
Line 461 - The title of Section 3.1 is "Intervals, Temporal Relations, and Sequences" with "Intervals" occurring as Section 3.1.2 and "Sequences-Combining Intervals" occurring as Section 3.1.4.
Line 452 - "The two expressions of a Temporal Relationship above are equivalent" appears after THREE examples of temporal relationships. To which two is this statement referring?
Line 395 - "Example" of "finishToFinish" does not appear to align with the "Definition".
Line 392-394 - it is unclear which elements are used from RFC 5988 from the list of elements in Section 6.2.2 of that RFC - explicitly clarify elements
Line 387 - The title of Section 3.1 is "Intervals, Temporal Relations, and Sequences" with "Intervals" occurring as Section 3.1.2 and "Sequences-Combining Intervals" occurring as Section 3.1.4. "Temporal Relations" is not explicitly Section 3.1.3.
Line 385-386 - This is the first occurrence of using "note" text after an example. The note text is actually useful to parse the example and would be better served before the example.
Line 277 - "While this specification the use of core semantic elements from iCalendar," is unclear as written.
Line 271 - "Practitioners should consult..." refers to practitioners of what exactly? WS-Calendar? "Which Time? UTS vs. Local Time"? - clarify "practitioners"
Line 229-236 - This italicized text appears to be a quote from a reference.
Line 209 - "This work provides the vocabulary..." is vague. To which work is it referring? Both preceding references? - clarify reference
Line 2673 - this item appears to be part of 5.2.3 - make this section 5.2.3.3 rather than 5.2.4 and rename to "Bound Intervals and Sequences in WS-Calendar"
Line 2662 - this item appears to align with item #5 in the bulleted list in 5.2 (line 2625) - make this section 5.2.5 and rename to "Semantic Conformance in WS-Calendar"
Line 2657-2661 - this text appears to align with item #4 in the bulleted list in 5.2 (line 2624) yet has no heading - add heading for this set of language: 5.2.4 Covarying Attributes
Line 2690-2697 - this section is listed as item #3 in the bulleted list in 5.2 (line 2623) yet appears after the #4 and #5 bulleted items - make this section 5.2.3
Line 1646 - table heading uses "aspects", column heading uses "element" - make consistent
Line 1022 - "Partitions are Sequences composed of consecutive Intervals" appears to be in conflict with line 180 "A Partition is a set of consecutive Intervals."
Line 1020 - does "availability" in the rules for Schedules and Availability mean "Availability" as defined in the document?
Line 1020 - is it "Designated Interval" or "designated Interval"? - employ correct term and make consistent throughout document
Line 887 - Rrule states that an interval can be bound by dtStart and dtEnd or by dtStart and Duration. However, Table 3-6 and 3-7 explicitly state that the pair dtStart/dtEnd is not allowed
Line 881, 887, 895 - the granularity discussion in Table 3-7 and 3-8 is inconsistent with the text in 895 with respec to "9:99" or "9:00"
Line 822, 834 - is it "Designated Interval" or "designated Interval"? - employ correct term and make consistent throughout document
Line 369-370 - The statement about "unanchored interval" both repeats the statement about "unscheduled interval" in 362-363 and appears to disagree with the definitions in 196 Table 1-6.
Line 175-177 - the practice of providing normative definitions in section 1.8, but perhaps extending/superseding/modifying later in the document as is stated practice, seems ill advised.
Line 2688 - missing text: "Still to come" probably not complete enough for conformance
Line 2639 - footnote states "This needs detailed discussion...". How can one be expected to conform to a rule that needs (further) discussion? - tighten the rule or delete
Line 858 - [RFC5998] is incorrect - SHOULD BE [RFC5545]
{"searchers":{"groups":[{"searchers":[{"name":"Project","id":"project","key":"issue.field.project","isShown":true,"lastViewed":1765965340511,"shown":true},{"name":"Summary","id":"summary","key":"issue.field.summary","isShown":true,"shown":true},{"name":"Type","id":"issuetype","key":"issue.field.issuetype","isShown":true,"lastViewed":1765965340519,"shown":true},{"name":"Status","id":"status","key":"issue.field.status","isShown":true,"lastViewed":1765965340528,"shown":true},{"name":"Priority","id":"priority","key":"issue.field.priority","isShown":true,"shown":true},{"name":"Resolution","id":"resolution","key":"issue.field.resolution","isShown":true,"shown":true},{"name":"Creator","id":"creator","key":"issue.field.creator","isShown":true,"shown":true},{"name":"Affects Version","id":"version","key":"issue.field.affectsversions","isShown":true,"shown":true},{"name":"Fix Version","id":"fixfor","key":"issue.field.fixversions","isShown":true,"shown":true},{"name":"Component","id":"component","key":"issue.field.components","isShown":true,"lastViewed":1765965340535,"shown":true},{"name":"% Limits","id":"workratio","key":"issue.field.workratio","isShown":true,"shown":true},{"name":"Link types","id":"issue_link_type","key":"issue.field.issuelinks","isShown":true,"shown":true},{"name":"Environment","id":"environment","key":"issue.field.environment","isShown":true,"shown":true},{"name":"Description","id":"description","key":"issue.field.description","isShown":true,"shown":true},{"name":"Comment","id":"comment","key":"issue.field.comment","isShown":true,"shown":true},{"name":"Label","id":"labels","key":"issue.field.labels","isShown":true,"shown":true},{"name":"Query","id":"text","key":"text","isShown":true,"shown":true},{"name":"Development","id":"customfield_10120","key":"com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary","isShown":true,"shown":true},{"name":"Epic Color","id":"customfield_10024","key":"com.pyxis.greenhopper.jira:gh-epic-color","isShown":false,"shown":false},{"name":"Epic Link","id":"customfield_10021","key":"com.pyxis.greenhopper.jira:gh-epic-link","isShown":true,"shown":true},{"name":"Epic Name","id":"customfield_10023","key":"com.pyxis.greenhopper.jira:gh-epic-label","isShown":true,"shown":true},{"name":"Epic Status","id":"customfield_10022","key":"com.pyxis.greenhopper.jira:gh-epic-status","isShown":false,"shown":false},{"name":"Epic/Theme","id":"customfield_10027","key":"com.atlassian.jira.plugin.system.customfieldtypes:labels","isShown":true,"shown":true},{"name":"Flagged","id":"customfield_10026","key":"com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes","isShown":true,"shown":true},{"name":"Original story points","id":"customfield_10224","key":"com.atlassian.jpo:jpo-custom-field-original-story-points","isShown":true,"shown":true},{"name":"Parent Link","id":"customfield_10221","key":"com.atlassian.jpo:jpo-custom-field-parent","isShown":false,"shown":false},{"name":"Proposal","id":"customfield_10001","key":"com.atlassian.jira.plugin.system.customfieldtypes:textarea","isShown":true,"shown":true},{"name":"Rank","id":"customfield_10025","key":"com.pyxis.greenhopper.jira:gh-lexo-rank","isShown":true,"shown":true},{"name":"Resolution","id":"customfield_10002","key":"com.atlassian.jira.plugin.system.customfieldtypes:textarea","isShown":true,"shown":true},{"name":"Sprint","id":"customfield_10020","key":"com.pyxis.greenhopper.jira:gh-sprint","isShown":true,"shown":true},{"name":"Story Points","id":"customfield_10028","key":"com.atlassian.jira.plugin.system.customfieldtypes:float","isShown":false,"shown":false},{"name":"Team","id":"customfield_10220","key":"com.atlassian.teams:rm-teams-custom-field-team","isShown":true,"shown":true}],"type":"DETAILS","title":"Details"},{"searchers":[{"name":"Created Date","id":"created","key":"issue.field.created","isShown":true,"shown":true},{"name":"Updated Date","id":"updated","key":"issue.field.updated","isShown":true,"shown":true},{"name":"Resolution Date","id":"resolutiondate","key":"issue.field.resolution.date","isShown":true,"shown":true},{"name":"Due Date","id":"duedate","key":"issue.field.duedate","isShown":true,"shown":true},{"name":"Target end","id":"customfield_10223","key":"com.atlassian.jpo:jpo-custom-field-baseline-end","isShown":true,"shown":true},{"name":"Target start","id":"customfield_10222","key":"com.atlassian.jpo:jpo-custom-field-baseline-start","isShown":true,"shown":true}],"type":"DATES","title":"Dates"},{"searchers":[{"name":"Assignee","id":"assignee","key":"issue.field.assignee","isShown":true,"lastViewed":1765965340530,"shown":true},{"name":"Reporter","id":"reporter","key":"issue.field.reporter","isShown":true,"shown":true}],"type":"PEOPLE","title":"People"}]},"values":{"issuetype":{"name":"Type","editHtml":"\n\n\n\n <div class=\"field-group aui-field-issuetype\" >\n <label for=\"searcher-type\">Type</label> <select class=\"select js-default-checkboxmultiselect\"\n id=\"searcher-type\"\n multiple=\"multiple\"\n name=\"type\"\n data-max-inline-results-displayed=\"100\"\n data-placeholder-text=\"Find Issue Types...\">\n <optgroup>\n \n <option class=\" \"\n id=\"type_-2\"\n title=\"All Standard Issue Types\"\n value=\"-2\">All Standard Issue Types</option>\n \n <option class=\" \"\n id=\"type_-3\"\n title=\"All Sub-Task Issue Types\"\n value=\"-3\">All Sub-Task Issue Types</option>\n </optgroup>\n\n <optgroup label=\"Standard Issue Types\">\n \n <option class=\" imagebacked 10021 \"\n data-icon=\"/secure/viewavatar?size=xsmall&avatarId=10303&avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_1\"\n title=\"Bug\"\n value=\"1\">Bug</option>\n \n <option class=\" imagebacked 10021 \"\n data-icon=\"/secure/viewavatar?size=xsmall&avatarId=10310&avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_4\"\n title=\"Improvement\"\n value=\"4\">Improvement</option>\n \n <option class=\" imagebacked 10021 \"\n data-icon=\"/secure/viewavatar?size=xsmall&avatarId=10311&avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_2\"\n title=\"New Feature\"\n value=\"2\">New Feature</option>\n \n <option class=\" imagebacked 10021 \"\n data-icon=\"/secure/viewavatar?size=xsmall&avatarId=10318&avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_3\"\n title=\"Task\"\n value=\"3\">Task</option>\n </optgroup>\n\n <optgroup label=\"Sub-Task Issue Types\">\n \n <option class=\" imagebacked 10021 \"\n data-icon=\"/secure/viewavatar?size=xsmall&avatarId=10316&avatarType=issuetype\"\n data-fallback-icon=\"/images/icons/issuetypes/blank.png\"\n id=\"type_5\"\n title=\"Sub-task\"\n value=\"5\">Sub-task</option>\n </optgroup>\n </select>\n </div>\n ","validSearcher":true,"isShown":true},"component":{"name":"Component","viewHtml":" <div class=\"searcherValue\">\n \n <label class=\"fieldLabel\" for=\"fieldcomponent\">Component:</label><span id=\"fieldcomponent\" class=\"fieldValue\">\n \n spec </span></div>\n","editHtml":"\n <div class=\"field-group aui-field-projectconstant\" >\n <label for=\"searcher-component\">Component</label> <select class=\"select js-default-checkboxmultiselectcomponent\"\n id=\"searcher-component\"\n multiple=\"multiple\"\n name=\"component\"\n data-max-inline-results-displayed=\"100\"\n aria-label=\"Search for components\">\n <optgroup label=\"\">\n <option value=\"-1\" title=\"No Component\">No Component</option>\n <option value=\"id:appendix\" title=\"appendix\">appendix</option>\n <option value=\"id:conform\" title=\"conform\">conform</option>\n <option value=\"id:MIN\" title=\"MIN\">MIN</option>\n <option value=\"id:model\" title=\"model\">model</option>\n <option value=\"id:PIM\" title=\"PIM\">PIM</option>\n <option value=\"id:rest\" title=\"rest\">rest</option>\n <option value=\"id:schema\" title=\"schema\">schema</option>\n <option value=\"id:soap\" title=\"soap\">soap</option>\n <option selected=\"selected\" value=\"id:spec\" title=\"spec\">spec</option>\n <option value=\"id:streams\" title=\"streams\">streams</option>\n <option value=\"id:White Paper\" title=\"White Paper\">White Paper</option>\n </optgroup>\n </select>\n </div>\n \n","jql":"component = spec","validSearcher":true,"isShown":true},"project":{"name":"Project","viewHtml":" <div class=\"searcherValue\">\n \n <label class=\"fieldLabel\" for=\"fieldpid\">Project:</label><span id=\"fieldpid\" class=\"fieldValue\">\n \n <a data-pid=\"10045\" data-issue-type-ids=\"\" href=\"/browse/WSCALENDAR\" title=\"Browse OASIS Web Services Calendar (WS-Calendar) TC project\">OASIS Web Services Calendar (WS-Calendar) TC</a> </span></div>\n","editHtml":" \n <div class=\"field-group aui-field-project\" >\n <label for=\"searcher-pid\">Project</label> <select class=\"js-project-checkboxmultiselect\"\n data-placeholder-text=\"Find Projects...\"\n id=\"searcher-pid\"\n multiple=\"multiple\"\n name=\"pid\">\n <optgroup label=\"Recent Projects\">\n </optgroup>\n <optgroup label=\"All Projects\" >\n <option data-icon=\"/secure/projectavatar?pid=10045&size=small\"\n selected=\"selected\" title=\"OASIS Web Services Calendar (WS-Calendar) TC\"\n value=\"10045\">\n OASIS Web Services Calendar (WS-Calendar) TC (WSCALENDAR)\n </option>\n \n <option data-icon=\"/secure/projectavatar?pid=10980&size=small\"\n title=\"Cyber Standards Council\"\n value=\"10980\">\n Cyber Standards Council (CYBERCOUNC)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=11280&size=small\"\n title=\"DocBook Style Sheet Development\"\n value=\"11280\">\n DocBook Style Sheet Development (DSSD)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=11680&size=small\"\n title=\"IT Operations\"\n value=\"11680\">\n IT Operations (IO)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10130&size=small\"\n title=\"OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC\"\n value=\"10130\">\n OASIS Advanced Message Queuing Protocol (AMQP) Bindings and Mappings (AMQP-BINDMAP) TC (AMQPBINDMAP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10082&size=small\"\n title=\"OASIS Advanced Message Queuing Protocol (AMQP) TC\"\n value=\"10082\">\n OASIS Advanced Message Queuing Protocol (AMQP) TC (AMQP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10083&size=small\"\n title=\"OASIS AMQP Member Section \"\n value=\"10083\">\n OASIS AMQP Member Section (AMQPMS)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=11080&size=small\"\n title=\"OASIS Business Document Exchange (BDXR) TC\"\n value=\"11080\">\n OASIS Business Document Exchange (BDXR) TC (BDXR)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10580&size=small\"\n title=\"OASIS Classification of Everyday Living (COEL) TC\"\n value=\"10580\">\n OASIS Classification of Everyday Living (COEL) TC (COEL)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10120&size=small\"\n title=\"OASIS Cloud Application Management for Platforms (CAMP) TC\"\n value=\"10120\">\n OASIS Cloud Application Management for Platforms (CAMP) TC (CAMP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10132&size=small\"\n title=\"OASIS Cloud Authorization (CloudAuthZ) TC\"\n value=\"10132\">\n OASIS Cloud Authorization (CloudAuthZ) TC (CLOUDAUTHZ)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10054&size=small\"\n title=\"OASIS Code List Representation TC\"\n value=\"10054\">\n OASIS Code List Representation TC (CODELIST)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10780&size=small\"\n title=\"OASIS Common Security Advisory Framework (CSAF) TC\"\n value=\"10780\">\n OASIS Common Security Advisory Framework (CSAF) TC (CSAF)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10021&size=small\"\n title=\"OASIS Content Management Interoperability Services (CMIS) TC\"\n value=\"10021\">\n OASIS Content Management Interoperability Services (CMIS) TC (CMIS)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=11181&size=small\"\n title=\"OASIS Cyber Threat Intelligence (CTI) TC\"\n value=\"11181\">\n OASIS Cyber Threat Intelligence (CTI) TC (CTI)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10131&size=small\"\n title=\"OASIS Darwin Information Typing Architecture (DITA) TC\"\n value=\"10131\">\n OASIS Darwin Information Typing Architecture (DITA) TC (DITA)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10070&size=small\"\n title=\"OASIS Dev Testing TC\"\n value=\"10070\">\n OASIS Dev Testing TC (DEVTEST)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10105&size=small\"\n title=\"OASIS Digital Signature Services eXtended (DSS-X) TC\"\n value=\"10105\">\n OASIS Digital Signature Services eXtended (DSS-X) TC (DSSX)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10880&size=small\"\n title=\"OASIS DITA Adoption TC\"\n value=\"10880\">\n OASIS DITA Adoption TC (DITAADOPT)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10042&size=small\"\n title=\"OASIS ebXML Core (ebCore) TC\"\n value=\"10042\">\n OASIS ebXML Core (ebCore) TC (EBCORE)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10102&size=small\"\n title=\"OASIS ebXML Messaging Services TC\"\n value=\"10102\">\n OASIS ebXML Messaging Services TC (EBXMLMSG)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10100&size=small\"\n title=\"OASIS ebXML Registry TC\"\n value=\"10100\">\n OASIS ebXML Registry TC (REGREPTC)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10086&size=small\"\n title=\"OASIS EDXL CAP\"\n value=\"10086\">\n OASIS EDXL CAP (CAPAU)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10084&size=small\"\n title=\"OASIS EDXL Distribution Element\"\n value=\"10084\">\n OASIS EDXL Distribution Element (EMFW)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10081&size=small\"\n title=\"OASIS EDXL Situation Reporting\"\n value=\"10081\">\n OASIS EDXL Situation Reporting (EMER)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10056&size=small\"\n title=\"OASIS Election and Voter Services TC\"\n value=\"10056\">\n OASIS Election and Voter Services TC (ELECTION)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10170&size=small\"\n title=\"OASIS Electronic Trial Master File (eTMF) Standard TC\"\n value=\"10170\">\n OASIS Electronic Trial Master File (eTMF) Standard TC (ETMF)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10151&size=small\"\n title=\"OASIS Emergency Management Adoption TC\"\n value=\"10151\">\n OASIS Emergency Management Adoption TC (EMERGENCYADOPT)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10181&size=small\"\n title=\"OASIS Emergency Management TC\"\n value=\"10181\">\n OASIS Emergency Management TC (EMERGENCY)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10047&size=small\"\n title=\"OASIS Energy Interoperation TC\"\n value=\"10047\">\n OASIS Energy Interoperation TC (ENERGYINTEROP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10046&size=small\"\n title=\"OASIS Energy Market Information Exchange (eMIX) TC\"\n value=\"10046\">\n OASIS Energy Market Information Exchange (eMIX) TC (EMIX)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10022&size=small\"\n title=\"OASIS eXtensible Access Control Markup Language (XACML) TC\"\n value=\"10022\">\n OASIS eXtensible Access Control Markup Language (XACML) TC (XACML)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10052&size=small\"\n title=\"OASIS Identity in the Cloud TC\"\n value=\"10052\">\n OASIS Identity in the Cloud TC (IDCLOUD)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10025&size=small\"\n title=\"OASIS Identity Metasystem Interoperability (IMI) TC\"\n value=\"10025\">\n OASIS Identity Metasystem Interoperability (IMI) TC (IMI)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10026&size=small\"\n title=\"OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC \"\n value=\"10026\">\n OASIS Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC (ICOM)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10029&size=small\"\n title=\"OASIS Key Management Interoperability Protocol (KMIP) TC\"\n value=\"10029\">\n OASIS Key Management Interoperability Protocol (KMIP) TC (KMIP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10480&size=small\"\n title=\"OASIS LegalDocumentML (LegalDocML) TC\"\n value=\"10480\">\n OASIS LegalDocumentML (LegalDocML) TC (LEGALDOCML)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10160&size=small\"\n title=\"OASIS LegalRuleML TC\"\n value=\"10160\">\n OASIS LegalRuleML TC (LEGALRULEML)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=11380&size=small\"\n title=\"OASIS LegalXML Electronic Court Filing TC`\"\n value=\"11380\">\n OASIS LegalXML Electronic Court Filing TC` (LEGALXMLCO)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10150&size=small\"\n title=\"OASIS Message Queuing Telemetry Transport (MQTT) TC\"\n value=\"10150\">\n OASIS Message Queuing Telemetry Transport (MQTT) TC (MQTT)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10681&size=small\"\n title=\"OASIS OCPP Electric Vehicle Charging Equipment Data Exchange TC\"\n value=\"10681\">\n OASIS OCPP Electric Vehicle Charging Equipment Data Exchange TC (OCPP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10140&size=small\"\n title=\"OASIS Open Building Information Exchange (oBIX) TC\"\n value=\"10140\">\n OASIS Open Building Information Exchange (oBIX) TC (OBIX)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10103&size=small\"\n title=\"OASIS Open Data Protocol (OData) TC\"\n value=\"10103\">\n OASIS Open Data Protocol (OData) TC (ODATA)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10027&size=small\"\n title=\"OASIS Open Document Format for Office Applications (OpenDocument) TC\"\n value=\"10027\">\n OASIS Open Document Format for Office Applications (OpenDocument) TC (OFFICE)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10023&size=small\"\n title=\"OASIS Open Document Format Interoperability and Conformance (OIC) TC\"\n value=\"10023\">\n OASIS Open Document Format Interoperability and Conformance (OIC) TC (OIC)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10380&size=small\"\n title=\"OASIS OSLC Lifecycle Integration Core (OSLC Core) TC\"\n value=\"10380\">\n OASIS OSLC Lifecycle Integration Core (OSLC Core) TC (OSLCCORE)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10182&size=small\"\n title=\"OASIS OSLC Lifecycle Integration for Automation (OSLC Automation) TC\"\n value=\"10182\">\n OASIS OSLC Lifecycle Integration for Automation (OSLC Automation) TC (OSLCAUTO)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10171&size=small\"\n title=\"OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC\"\n value=\"10171\">\n OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC (OSLCCCM)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10184&size=small\"\n title=\"OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery\"\n value=\"10184\">\n OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery (OSLCPROMCO)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10152&size=small\"\n title=\"OASIS PKCS 11 TC\"\n value=\"10152\">\n OASIS PKCS 11 TC (PKCS)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10280&size=small\"\n title=\"OASIS Privacy by Design Documentation for Software Engineers (PbD-SE) TC\"\n value=\"10280\">\n OASIS Privacy by Design Documentation for Software Engineers (PbD-SE) TC (PBDSE)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10041&size=small\"\n title=\"OASIS Security Services (SAML) TC\"\n value=\"10041\">\n OASIS Security Services (SAML) TC (SECURITY)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10090&size=small\"\n title=\"OASIS Service Component Architecture / Assembly (SCA-Assembly) TC\"\n value=\"10090\">\n OASIS Service Component Architecture / Assembly (SCA-Assembly) TC (SCAASSEMBLY)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10091&size=small\"\n title=\"OASIS Service Component Architecture / Bindings (SCA-Bindings) TC\"\n value=\"10091\">\n OASIS Service Component Architecture / Bindings (SCA-Bindings) TC (SCABINDINGS)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10092&size=small\"\n title=\"OASIS Service Component Architecture / BPEL (SCA-BPEL) TC\"\n value=\"10092\">\n OASIS Service Component Architecture / BPEL (SCA-BPEL) TC (SCABPEL)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10088&size=small\"\n title=\"OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC\"\n value=\"10088\">\n OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC (SCACANDCPP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10093&size=small\"\n title=\"OASIS Service Component Architecture / J (SCA-J) TC\"\n value=\"10093\">\n OASIS Service Component Architecture / J (SCA-J) TC (SCAJ)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10089&size=small\"\n title=\"OASIS Service Component Architecture / Policy (SCA-Policy) TC\"\n value=\"10089\">\n OASIS Service Component Architecture / Policy (SCA-Policy) TC (SCAPOLICY)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10048&size=small\"\n title=\"OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC\"\n value=\"10048\">\n OASIS Service-Oriented Architecture End-to-End Resource Planning (SOA-EERP) TC (SOAEERP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10043&size=small\"\n title=\"OASIS SOA Reference Model TC\"\n value=\"10043\">\n OASIS SOA Reference Model TC (SOARM)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10055&size=small\"\n title=\"OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC\"\n value=\"10055\">\n OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC (SRAMP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10024&size=small\"\n title=\"OASIS Solution Deployment Descriptor (SDD) TC\"\n value=\"10024\">\n OASIS Solution Deployment Descriptor (SDD) TC (SDD)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10060&size=small\"\n title=\"OASIS Symptoms Automation Framework (SAF) TC\"\n value=\"10060\">\n OASIS Symptoms Automation Framework (SAF) TC (SAF)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10049&size=small\"\n title=\"OASIS Test Assertions Guidelines (TAG) TC\"\n value=\"10049\">\n OASIS Test Assertions Guidelines (TAG) TC (TAG)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10085&size=small\"\n title=\"OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC\"\n value=\"10085\">\n OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC (TOSCA)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10183&size=small\"\n title=\"OASIS Universal Business Language (UBL) TC\"\n value=\"10183\">\n OASIS Universal Business Language (UBL) TC (UBL)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10061&size=small\"\n title=\"OASIS Unstructured Operation Markup Language eXtended (UOML-X) TC\"\n value=\"10061\">\n OASIS Unstructured Operation Markup Language eXtended (UOML-X) TC (UOMLX)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10161&size=small\"\n title=\"OASIS Virtual I/O Device (VIRTIO) TC\"\n value=\"10161\">\n OASIS Virtual I/O Device (VIRTIO) TC (VIRTIO)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10087&size=small\"\n title=\"OASIS Web Experience Management Interoperability (WEMI) TC\"\n value=\"10087\">\n OASIS Web Experience Management Interoperability (WEMI) TC (WEMI)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10110&size=small\"\n title=\"OASIS Web Services Basic Reliable and Secure Profiles (WS-BRSP) TC\"\n value=\"10110\">\n OASIS Web Services Basic Reliable and Secure Profiles (WS-BRSP) TC (WSBRSP)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10031&size=small\"\n title=\"OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TC\"\n value=\"10031\">\n OASIS Web Services Discovery and Web Services Devices Profile (WS-DD) TC (WSDD)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10044&size=small\"\n title=\"OASIS Web Services Secure Exchange (WS-SX) TC\"\n value=\"10044\">\n OASIS Web Services Secure Exchange (WS-SX) TC (WSSX)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10053&size=small\"\n title=\"OASIS Web Services Security Maintenance (WSS-M) TC\"\n value=\"10053\">\n OASIS Web Services Security Maintenance (WSS-M) TC (WSSM)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10680&size=small\"\n title=\"OASIS XML Localisation Interchange File Format (XLIFF) TC\"\n value=\"10680\">\n OASIS XML Localisation Interchange File Format (XLIFF) TC (XLIFF)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10051&size=small\"\n title=\"OASIS XRI Data Interchange (XDI) TC\"\n value=\"10051\">\n OASIS XRI Data Interchange (XDI) TC (XDI)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10104&size=small\"\n title=\"Technical Advisory Board\"\n value=\"10104\">\n Technical Advisory Board (TAB)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10010&size=small\"\n title=\"Technical Committee Administration\"\n value=\"10010\">\n Technical Committee Administration (TCADMIN)\n </option>\n <option data-icon=\"/secure/projectavatar?pid=10101&size=small\"\n title=\"Z OASIS Liaisons\"\n value=\"10101\">\n Z OASIS Liaisons (LIAISONS)\n </option>\n </optgroup>\n </select>\n </div>\n \n\n","jql":"project = \"10045\"","validSearcher":true,"isShown":true},"assignee":{"name":"Assignee","editHtml":"\n \n <div class=\"field-group aui-field-userlist\" >\n <label for=\"searcher-assigneeSelect\">Assignee</label> <fieldset rel=\"assignee\" class=\"hidden user-group-searcher-params\">\n </fieldset>\n <select class=\"js-usergroup-checkboxmultiselect\" multiple=\"multiple\" id=\"assignee\" name=\"assignee\" data-placeholder-text=\"Enter username or group\">\n <optgroup>\n <option class=\"headerOption\" data-icon=\"https://issues.oasis-open.org/secure/useravatar?size=xsmall&avatarId=10123\" value=\"empty\" title=\"Unassigned\">Unassigned</option>\n </optgroup>\n <optgroup>\n </optgroup>\n </select>\n <input type=\"hidden\" name=\"check_prev_assignee\" value=\"true\">\n </div>\n \n","validSearcher":true,"isShown":true},"status":{"name":"Status","editHtml":"\n <div class=\"field-group aui-field-constants\" >\n <label for=\"searcher-status\">Status</label> <select class=\"select js-default-checkboxmultiselectstatuslozenge\"\n data-placeholder-text=\"Find Statuses...\"\n id=\"searcher-status\"\n multiple=\"multiple\"\n name=\"status\"\n data-max-inline-results-displayed=\"100\"\n data-footer-text=\"-94 more options. Continue typing to refine further.\" data-status-lozenge=\"true\">\n <optgroup >\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/open.png\" value=\"1\" title=\"Open\" data-simple-status=\"{"id":"1","name":"Open","description":"The issue is open and ready for the assignee to start work on it.","iconUrl":"/images/icons/statuses/open.png","statusCategory":{"id":2,"key":"new","colorName":"default"}}\">Open</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/resolved.png\" value=\"5\" title=\"Resolved\" data-simple-status=\"{"id":"5","name":"Resolved","description":"A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.","iconUrl":"/images/icons/statuses/resolved.png","statusCategory":{"id":3,"key":"done","colorName":"success"}}\">Resolved</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/closed.png\" value=\"6\" title=\"Closed\" data-simple-status=\"{"id":"6","name":"Closed","description":"The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.","iconUrl":"/images/icons/statuses/closed.png","statusCategory":{"id":3,"key":"done","colorName":"success"}}\">Closed</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/assigned.png\" value=\"10000\" title=\"New\" data-simple-status=\"{"id":"10000","name":"New","description":"","iconUrl":"/images/icons/statuses/assigned.png","statusCategory":{"id":2,"key":"new","colorName":"default"}}\">New</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/down.png\" value=\"10001\" title=\"Deferred\" data-simple-status=\"{"id":"10001","name":"Deferred","description":"","iconUrl":"/images/icons/statuses/down.png","statusCategory":{"id":4,"key":"indeterminate","colorName":"inprogress"}}\">Deferred</option>\n <option class=\"imagebacked\" data-icon=\"/images/icons/statuses/document.png\" value=\"10002\" title=\"Applied\" data-simple-status=\"{"id":"10002","name":"Applied","description":"","iconUrl":"/images/icons/statuses/document.png","statusCategory":{"id":4,"key":"indeterminate","colorName":"inprogress"}}\">Applied</option>\n </optgroup>\n</select>\n </div>\n \n","validSearcher":true,"isShown":true}}}
[{"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