Uploaded image for project: 'ejabberd development'
  1. ejabberd development
  2. EJAB-673

Support of collection node subscription options

    Details

      Description

      Currently one can subscribe to collection node, but not with options. There exists 2 options specific to collection nodes: pubsub#subscription_type and pubsub#subscription_depth.

      The XEP-0060 writes about this [1]:

      A service that implements collection nodes SHOULD allow entities to subscribe to collection nodes (subject to access models and local security policies).

      In addition to the subscription configuration options already defined, there are two subscription configuration options specific to collection nodes:

      So let's say this is not a bug, nor a new feature, but an improvement (else change issue type).
      Currently if I try to subscribe to a collection node with these options, it is rejected:

      <iq type='set'
          from='test@localhost.net/Gajim'
          to='pubsub.localhost.net'
          id='collsub2'>
        <pubsub xmlns='http://jabber.org/protocol/pubsub'>
          <subscribe jid='test@localhost.net'
      	       node='home/localhost.net/supertest/somenode/superblog2/comments'/>
          <options>
            <x xmlns='jabber:x:data' type='submit'>
      	<field var='FORM_TYPE' type='hidden'>
      	  <value>http://jabber.org/protocol/pubsub#subscribe_options</value>
      	</field>
      	<field var='pubsub#subscription_type'>
      	  <value>items</value>
      	</field>
      	<field var='pubsub#subscription_depth'>
      	  <value>all</value>
      	</field>
            </x>
          </options>
        </pubsub>
      </iq>
      
      <iq from='pubsub.localhost.net'
          to='test@localhost.net/Gajim'
          type='error' xml:lang='fr'
          id='collsub2'>
        <pubsub xmlns='http://jabber.org/protocol/pubsub'>
          <subscribe jid='test@localhost.net'
      	       node='home/localhost.net/supertest/somenode/superblog2/comments'/>
          <options>
            <x xmlns='jabber:x:data' type='submit'>
      	<field var='FORM_TYPE' type='hidden'>
      	  <value>http://jabber.org/protocol/pubsub#subscribe_options</value>
      	</field>
      	<field var='pubsub#subscription_type'>
      	  <value>items</value>
      	</field>
      	<field var='pubsub#subscription_depth'>
      	  <value>all</value>
      	</field>
            </x>
          </options>
        </pubsub>
        <error code='400' type='modify'>
          <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
        </error>
      </iq>
      

      If I do the same, without the options, it works.

      <iq type='set'
          from='test@localhost.net/Gajim'
          to='pubsub.localhost.net'
          id='collsub2'>
        <pubsub xmlns='http://jabber.org/protocol/pubsub'>
          <subscribe jid='test@localhost.net'
      	       node='home/localhost.net/supertest/somenode/superblog2/comments'/>
        </pubsub>
      </iq>
      
      <iq from='pubsub.localhost.net'
          to='test@localhost.net/Gajim'
          id='collsub2'
          type='result'>
        <subscription node='/home/localhost.net/supertest/somenode/superblog2/comments'
      		jid='test@localhost.net'
      		subscription='subscribed'
      		subid='4BE65CA677F5'/>
      </iq>
      
      <message from='pubsub.localhost.net' to='test2@localhost.net'>
        <event xmlns='http://jabber.org/protocol/pubsub#event'>
          <items node='/home/localhost.net/supertest/somenode/superblog2/comments'/>
        </event>
      </message>
      

      But then I don't receive the items published in /home/localhost.net/supertest/somenode/superblog2/comments and I am so sad about this.

      [1] http://www.xmpp.org/extensions/xep-0060.html#collections-subscribe

        Issue Links

          Activity

          jehan Jehan Hysseo created issue -
          mremond@process-one.net Mickaël Rémond made changes -
          Field Original Value New Value
          Description Currently one can subscribe to collection node, but not with options. There exists 2 options specific to collection nodes: pubsub#subscription_type and pubsub#subscription_depth.

          The XEP-0060 writes about this:

          -------------
          A service that implements collection nodes SHOULD allow entities to subscribe to collection nodes (subject to access models and local security policies).
          In addition to the subscription configuration options already defined, there are two subscription configuration options specific to collection nodes:
          -------------

          So let's say this is not a bug, nor a new feature, but an improvement (else change issue type).
          Currently if I try to subscribe to a collection node with these options, it is rejected:

          ------------
          <iq type='set'
          from='test at zemarmot net/Gajim'
          to='pubsub.zemarmot.net'
          id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net'
          node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          <options>
          <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
          </x>
          </options>
          </pubsub>
          </iq>

          <iq from='pubsub.zemarmot.net' to='test at zemarmot net/Gajim' type='error' xml:lang='fr' id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net' node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          <options>
          <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
          </x>
          </options>
          </pubsub>
          <error code='400' type='modify'>
          <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
          </error>
          </iq>
          ---------------

          If I do the same, without the options, it works.


          --------------------
          <iq type='set'
          from='test at zemarmot net/Gajim'
          to='pubsub.zemarmot.net'
          id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net'
          node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          </pubsub>
          </iq>

          <iq from='pubsub.zemarmot.net' to='test at zemarmot net/Gajim' id='collsub2' type='result'>
          <subscription node='/home/zemarmot.net/supertest/somenode/superblog2/comments' jid='test at zemarmot net' subscription='subscribed' subid='4BE65CA677F5'/>
          </iq>
          <message from='pubsub.zemarmot.net' to='jehan@zemarmot.net'>
          <event xmlns='http://jabber.org/protocol/pubsub#event&#39;>
          <items node='/home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          </event>
          </message>
          --------------------

          But then I don't receive the items published in /home/zemarmot.net/supertest/somenode/superblog2/comments and I am so sad about this. ;-)
          Currently one can subscribe to collection node, but not with options. There exists 2 options specific to collection nodes: pubsub#subscription_type and pubsub#subscription_depth.

          The XEP-0060 writes about this:

          -------------
          A service that implements collection nodes SHOULD allow entities to subscribe to collection nodes (subject to access models and local security policies).
          In addition to the subscription configuration options already defined, there are two subscription configuration options specific to collection nodes:
          -------------

          So let's say this is not a bug, nor a new feature, but an improvement (else change issue type).
          Currently if I try to subscribe to a collection node with these options, it is rejected:

          ------------
          <iq type='set'
          from='test at zemarmot net/Gajim'
          to='pubsub.zemarmot.net'
          id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net'
          node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          <options>
          <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
          </x>
          </options>
          </pubsub>
          </iq>

          <iq from='pubsub.zemarmot.net' to='test at zemarmot net/Gajim' type='error' xml:lang='fr' id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net' node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          <options>
          <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
          </x>
          </options>
          </pubsub>
          <error code='400' type='modify'>
          <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
          </error>
          </iq>
          ---------------

          If I do the same, without the options, it works.


          --------------------
          <iq type='set'
          from='test at zemarmot net/Gajim'
          to='pubsub.zemarmot.net'
          id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net'
          node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          </pubsub>
          </iq>

          <iq from='pubsub.zemarmot.net' to='test at zemarmot net/Gajim' id='collsub2' type='result'>
          <subscription node='/home/zemarmot.net/supertest/somenode/superblog2/comments' jid='test at zemarmot net' subscription='subscribed' subid='4BE65CA677F5'/>
          </iq>
          <message from='pubsub.zemarmot.net' to='test2 at zemarmot.net'>
          <event xmlns='http://jabber.org/protocol/pubsub#event&#39;>
          <items node='/home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          </event>
          </message>
          --------------------

          But then I don't receive the items published in /home/zemarmot.net/supertest/somenode/superblog2/comments and I am so sad about this. ;-)
          badlop Badlop made changes -
          Summary support of collection node subscription options Support of collection node subscription options
          Description Currently one can subscribe to collection node, but not with options. There exists 2 options specific to collection nodes: pubsub#subscription_type and pubsub#subscription_depth.

          The XEP-0060 writes about this:

          -------------
          A service that implements collection nodes SHOULD allow entities to subscribe to collection nodes (subject to access models and local security policies).
          In addition to the subscription configuration options already defined, there are two subscription configuration options specific to collection nodes:
          -------------

          So let's say this is not a bug, nor a new feature, but an improvement (else change issue type).
          Currently if I try to subscribe to a collection node with these options, it is rejected:

          ------------
          <iq type='set'
          from='test at zemarmot net/Gajim'
          to='pubsub.zemarmot.net'
          id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net'
          node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          <options>
          <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
          </x>
          </options>
          </pubsub>
          </iq>

          <iq from='pubsub.zemarmot.net' to='test at zemarmot net/Gajim' type='error' xml:lang='fr' id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net' node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          <options>
          <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
          </x>
          </options>
          </pubsub>
          <error code='400' type='modify'>
          <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
          </error>
          </iq>
          ---------------

          If I do the same, without the options, it works.


          --------------------
          <iq type='set'
          from='test at zemarmot net/Gajim'
          to='pubsub.zemarmot.net'
          id='collsub2'>
          <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
          <subscribe jid='test at zemarmot net'
          node='home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          </pubsub>
          </iq>

          <iq from='pubsub.zemarmot.net' to='test at zemarmot net/Gajim' id='collsub2' type='result'>
          <subscription node='/home/zemarmot.net/supertest/somenode/superblog2/comments' jid='test at zemarmot net' subscription='subscribed' subid='4BE65CA677F5'/>
          </iq>
          <message from='pubsub.zemarmot.net' to='test2 at zemarmot.net'>
          <event xmlns='http://jabber.org/protocol/pubsub#event&#39;>
          <items node='/home/zemarmot.net/supertest/somenode/superblog2/comments'/>
          </event>
          </message>
          --------------------

          But then I don't receive the items published in /home/zemarmot.net/supertest/somenode/superblog2/comments and I am so sad about this. ;-)
          Currently one can subscribe to collection node, but not with options. There exists 2 options specific to collection nodes: pubsub#subscription_type and pubsub#subscription_depth.

          The XEP-0060 writes about this:
          {quote}
          A service that implements collection nodes SHOULD allow entities to subscribe to collection nodes (subject to access models and local security policies).
          In addition to the subscription configuration options already defined, there are two subscription configuration options specific to collection nodes:
          {quote}

          So let's say this is not a bug, nor a new feature, but an improvement (else change issue type).
          Currently if I try to subscribe to a collection node with these options, it is rejected:

          {code:xml}
          <iq type='set'
              from='test@localhost.net/Gajim'
              to='pubsub.localhost.net'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
              <options>
                <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
                </x>
              </options>
            </pubsub>
          </iq>

          <iq from='pubsub.localhost.net'
              to='test@localhost.net/Gajim'
              type='error' xml:lang='fr'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
              <options>
                <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
                </x>
              </options>
            </pubsub>
            <error code='400' type='modify'>
              <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
            </error>
          </iq>
          {code}

          If I do the same, without the options, it works.
          {code:xml}
          <iq type='set'
              from='test@localhost.net/Gajim'
              to='pubsub.localhost.net'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
            </pubsub>
          </iq>

          <iq from='pubsub.localhost.net'
              to='test@localhost.net/Gajim'
              id='collsub2'
              type='result'>
            <subscription node='/home/localhost.net/supertest/somenode/superblog2/comments'
          jid='test@localhost.net'
          subscription='subscribed'
          subid='4BE65CA677F5'/>
          </iq>

          <message from='pubsub.localhost.net' to='test2@localhost.net'>
            <event xmlns='http://jabber.org/protocol/pubsub#event&#39;>
              <items node='/home/localhost.net/supertest/somenode/superblog2/comments'/>
            </event>
          </message>
          {code}

          But then I don't receive the items published in /home/localhost.net/supertest/somenode/superblog2/comments and I am so sad about this. ;-)
          Assignee Christophe Romain [ cromain ]
          badlop Badlop made changes -
          Description Currently one can subscribe to collection node, but not with options. There exists 2 options specific to collection nodes: pubsub#subscription_type and pubsub#subscription_depth.

          The XEP-0060 writes about this:
          {quote}
          A service that implements collection nodes SHOULD allow entities to subscribe to collection nodes (subject to access models and local security policies).
          In addition to the subscription configuration options already defined, there are two subscription configuration options specific to collection nodes:
          {quote}

          So let's say this is not a bug, nor a new feature, but an improvement (else change issue type).
          Currently if I try to subscribe to a collection node with these options, it is rejected:

          {code:xml}
          <iq type='set'
              from='test@localhost.net/Gajim'
              to='pubsub.localhost.net'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
              <options>
                <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
                </x>
              </options>
            </pubsub>
          </iq>

          <iq from='pubsub.localhost.net'
              to='test@localhost.net/Gajim'
              type='error' xml:lang='fr'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
              <options>
                <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
                </x>
              </options>
            </pubsub>
            <error code='400' type='modify'>
              <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
            </error>
          </iq>
          {code}

          If I do the same, without the options, it works.
          {code:xml}
          <iq type='set'
              from='test@localhost.net/Gajim'
              to='pubsub.localhost.net'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
            </pubsub>
          </iq>

          <iq from='pubsub.localhost.net'
              to='test@localhost.net/Gajim'
              id='collsub2'
              type='result'>
            <subscription node='/home/localhost.net/supertest/somenode/superblog2/comments'
          jid='test@localhost.net'
          subscription='subscribed'
          subid='4BE65CA677F5'/>
          </iq>

          <message from='pubsub.localhost.net' to='test2@localhost.net'>
            <event xmlns='http://jabber.org/protocol/pubsub#event&#39;>
              <items node='/home/localhost.net/supertest/somenode/superblog2/comments'/>
            </event>
          </message>
          {code}

          But then I don't receive the items published in /home/localhost.net/supertest/somenode/superblog2/comments and I am so sad about this. ;-)
          Currently one can subscribe to collection node, but not with options. There exists 2 options specific to collection nodes: pubsub#subscription_type and pubsub#subscription_depth.

          The XEP-0060 writes about this [1]:
          {quote}
          A service that implements collection nodes SHOULD allow entities to subscribe to collection nodes (subject to access models and local security policies).

          In addition to the subscription configuration options already defined, there are two subscription configuration options specific to collection nodes:
          {quote}

          So let's say this is not a bug, nor a new feature, but an improvement (else change issue type).
          Currently if I try to subscribe to a collection node with these options, it is rejected:

          {code:xml}
          <iq type='set'
              from='test@localhost.net/Gajim'
              to='pubsub.localhost.net'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
              <options>
                <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
                </x>
              </options>
            </pubsub>
          </iq>

          <iq from='pubsub.localhost.net'
              to='test@localhost.net/Gajim'
              type='error' xml:lang='fr'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
              <options>
                <x xmlns='jabber:x:data' type='submit'>
          <field var='FORM_TYPE' type='hidden'>
          <value>http://jabber.org/protocol/pubsub#subscribe_options&lt;/value>
          </field>
          <field var='pubsub#subscription_type'>
          <value>items</value>
          </field>
          <field var='pubsub#subscription_depth'>
          <value>all</value>
          </field>
                </x>
              </options>
            </pubsub>
            <error code='400' type='modify'>
              <bad-request xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
            </error>
          </iq>
          {code}

          If I do the same, without the options, it works.
          {code:xml}
          <iq type='set'
              from='test@localhost.net/Gajim'
              to='pubsub.localhost.net'
              id='collsub2'>
            <pubsub xmlns='http://jabber.org/protocol/pubsub&#39;>
              <subscribe jid='test@localhost.net'
          node='home/localhost.net/supertest/somenode/superblog2/comments'/>
            </pubsub>
          </iq>

          <iq from='pubsub.localhost.net'
              to='test@localhost.net/Gajim'
              id='collsub2'
              type='result'>
            <subscription node='/home/localhost.net/supertest/somenode/superblog2/comments'
          jid='test@localhost.net'
          subscription='subscribed'
          subid='4BE65CA677F5'/>
          </iq>

          <message from='pubsub.localhost.net' to='test2@localhost.net'>
            <event xmlns='http://jabber.org/protocol/pubsub#event&#39;>
              <items node='/home/localhost.net/supertest/somenode/superblog2/comments'/>
            </event>
          </message>
          {code}

          But then I don't receive the items published in /home/localhost.net/supertest/somenode/superblog2/comments and I am so sad about this. ;-)

          [1] http://www.xmpp.org/extensions/xep-0060.html#collections-subscribe
          cromain@process-one.net Christophe Romain (Inactive) made changes -
          Fix Version/s ejabberd 2.1.0 [ 10140 ]
          Fix Version/s ejabberd 3.0-alpha [ 10240 ]
          cromain@process-one.net Christophe Romain (Inactive) made changes -
          Fix Version/s ejabberd-3.1.0 [ 10281 ]
          Fix Version/s ejabberd 2.1.0 [ 10140 ]
          Fix Version/s ejabberd 3.0.0-alpha [ 10240 ]
          cromain@process-one.net Christophe Romain (Inactive) made changes -
          Fix Version/s ejabberd 2.1.0 [ 10140 ]
          Fix Version/s ejabberd 3.0.0-alpha [ 10240 ]
          Fix Version/s ejabberd-3.1.0 [ 10281 ]
          cromain@process-one.net Christophe Romain (Inactive) made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Duplicate [ 3 ]
          cromain@process-one.net Christophe Romain (Inactive) made changes -
          Link This issue duplicates EJAB-815 [ EJAB-815 ]
          cromain@process-one.net Christophe Romain (Inactive) made changes -
          Link This issue duplicates EJAB-845 [ EJAB-845 ]
          mremond@process-one.net Mickaël Rémond made changes -
          Workflow development v3 [ 58062 ] Development v4 [ 80947 ]

            People

            • Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development