<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:00 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[YANGTOOLS-684] [Yang 1.1] Add support for new statement &quot;action&quot;</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-684</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description></description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="23104">YANGTOOLS-684</key>
            <summary>[Yang 1.1] Add support for new statement &quot;action&quot;</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="ifoltin">Igor Foltin</assignee>
                                    <reporter username="pkajsa">Peter Kajsa</reporter>
                        <labels>
                    </labels>
                <created>Fri, 7 Oct 2016 08:33:43 +0000</created>
                <updated>Sun, 10 Apr 2022 18:35:53 +0000</updated>
                            <resolved>Mon, 19 Dec 2016 09:26:23 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="44180" author="martin.ciglan" created="Wed, 19 Oct 2016 12:18:11 +0000"  >&lt;p&gt;RFC7950:&lt;br/&gt;
7.15. The &quot;action&quot; Statement&lt;br/&gt;
 The &quot;action&quot; statement is used to define an operation connected to a&lt;br/&gt;
 specific container or list data node. It takes one argument, which&lt;br/&gt;
 is an identifier, followed by a block of substatements that holds&lt;br/&gt;
 detailed action information. The argument is the name of the action.&lt;br/&gt;
 The &quot;action&quot; statement defines an action node in the schema tree.&lt;br/&gt;
 Under the action node, a schema node with the name &quot;input&quot; and a&lt;br/&gt;
 schema node with the name &quot;output&quot; are also defined. The nodes&lt;br/&gt;
 &quot;input&quot; and &quot;output&quot; are defined in the module&#8217;s namespace.&lt;br/&gt;
 An action MUST NOT be defined within an rpc, another action, or a&lt;br/&gt;
 notification, i.e., an action node MUST NOT have an rpc, action, or a&lt;br/&gt;
 notification node as one of its ancestors in the schema tree. For&lt;br/&gt;
 example, this means that it is an error if a grouping that contains&lt;br/&gt;
 an action somewhere in its node hierarchy is used in a notification&lt;br/&gt;
 definition.&lt;br/&gt;
 An action MUST NOT have any ancestor node that is a list node without&lt;br/&gt;
 a &quot;key&quot; statement.&lt;br/&gt;
 Since an action cannot be defined at the top level of a module or in&lt;br/&gt;
 a &quot;case&quot; statement, it is an error if a grouping that contains an&lt;br/&gt;
 action at the top of its node hierarchy is used at the top level of a&lt;br/&gt;
 module or in a case definition.&lt;br/&gt;
 The difference between an action and an rpc is that an action is tied&lt;br/&gt;
 to a node in the datastore, whereas an rpc is not. When an action is&lt;br/&gt;
 invoked, the node in the datastore is specified along with the name&lt;br/&gt;
 of the action and the input parameters.&lt;/p&gt;</comment>
                            <comment id="44181" author="ifoltin" created="Mon, 7 Nov 2016 12:11:43 +0000"  >&lt;p&gt;API change - &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/48035/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/48035/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="44182" author="ifoltin" created="Tue, 13 Dec 2016 20:17:13 +0000"  >&lt;p&gt;Implementation - &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/49320/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/49320/&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="21311">NETCONF-298</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="22775">YANGTOOLS-355</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="23084">YANGTOOLS-664</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23119">YANGTOOLS-699</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6896</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=6896]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10308"><![CDATA[New Feature]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10357"><![CDATA[Carbon-M3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i028qv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>