Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-25890

Documentation: UNIX-based installation Guide must be reviewed

    Details

      Description

      There are some inconsistencies on the Installation Guide for Unix-based Systems documentation page.

      MySQL install section does not make sense

      Download from the official MySQL webpage is strongly recommended.

      Why we strongly recommend customers to download MySQL from their website instead using the standard packages of their distributions with
      which our software was tested?

      Besides the testing, it's important to remember that we must provide support and reproduce customer bugs and as closer their environment is to testing and support environments, the better.

      PHP set up incomplete

      This step requires the modification of two files: Apache2 configuration file and php.ini.
      These files can be edited using a terminal editor like vi or nano, or a simple text editor such as TextEdit or Atom.

      The steps described in this howto to install php is incomplete and won't make sense to the supported platforms - maybe in MacOs only - and shouldn't be here.

      The paths are non standard

      According to the Requirements & System Configuration page, the recommended setups should be Debian, Ubuntu or RHEL / CentOS.

      The paths on the page are not the ones used in neither of these systems and should be fixed.

      sudo vi /private/etc/apache2/httpd.conf
      sudo vi /private/etc/apache2/users/ez1.lh.conf

      • In the first case, the path should probably be /etc/apache2/apache2.conf in Debian and /etc/httpd/httpd.conf in CentOS.
      • In the second one, /etc/apache2/apache2.conf in Debian and /etc/httpd/conf.d in CentOS.

      MacOS is not a supported platform and should not be used in documentation

      Apache setup

      b. Uncomment and modify the following lines:

      LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
      LoadModule rewrite_module libexec/apache2/mod_rewrite.so

      This does not make sense since Debian, for example, uses a2enmod to enable modules. But the main reason is we shouldn't explain how to enable modules, we should just list them as required on the Requirements page.

      Hosts file configuration

      This step is allows you to use ez1.lh as an address to access running Platform from a web browser. You can substitute the address with the address you intend to use to access your installation (remember to change it in all other command on this page as well):

      This is something only makes sense in a development environment. It should be removed from the official documentation.

      Composer should not be installed this way

      mv composer.phar /usr/local/bin/composer

      I remember some time ago we - engineering - talked about having the documentation with a composer alias or the full command php -d memory_limit=-1 composer.phar and the decision was stay with the full command to have a safe standard. This rule should be kept here and in the documentation.

      Install additional requirements for eZ Platform

      cd /usr/lib/php
      sudo php install-pear-nozlib.phar

      • If the steps described here are mandatory, why they are not described in the INSTALL.md file? I think they are not.
      • The steps does not explain how to obtain the install-pear-nozlib.phar file and so they won't work.

      apt-get install icu4c
      sudo pecl install intl

      • Again, we shouldn't explain how to install packages but list them as required on the Requirements. Besides, I think icu4c won't even exist in Debian and CentOs.

      Install eZ Platform

      git clone https://github.com/ezsystems/ezplatform.git

      The steps listed here are very different from the ones described in the INSTALL.md file what is very confusing, specially for customers since the Manual Installation Guides page instructs them to download the software from share.ez.no/downloads/downloads.

      Modify virtual host file based on dev environment

      • The steps listed here should follow the lead on Apache 2.2 / 2.4 configuration.
      • Listing a virtual host file here may result in compatibility and maintenance problems. Instead, we should link it to the vhost.template on Github.

      Install required dependencies using Composer

      composer install

      Again the full form should be used.

      Invalid permissions

      sudo chmod +a "_www allow delete,write,append,file_inherit,directory_inherit" app/{cache,logs,config} web

      Afaik, these are MacOS only - see Mac OS Man page - and shouldn't be here.

      Optional steps

      Some of these steps does not make sense to Debian or CentOS.

        Issue Links

          Activity

          Eduardo Fernandes (Inactive) created issue -
          Eduardo Fernandes (Inactive) made changes -
          Field Original Value New Value
          Summary Documentation: Installation Guide must be reviewd Documentation: Installation Guide must be reviewed
          Eduardo Fernandes (Inactive) made changes -
          Description There are some inconsistencies on the [Installation Guide for Unix-based Systems|https://doc.ez.no/display/DEVELOPER/Installation+Guide+for+Unix-based+Systems] documentation page.

          h2. MySQL install section does not make sense
          {quote}Download from the official MySQL webpage is strongly recommended.{quote}

          Why we *strongly recommend* customers to download MySQL from their website instead using the standard packages of their distributions with
          which our software was tested?

          Besides the testing, it's important to remember that we *must provide* support and reproduce customer bugs and as closer their environment is to testing and support environments, the better.

          h2. PHP set up incomplete
          {quote}This step requires the modification of two files: Apache2 configuration file and php.ini.
          These files can be edited using a terminal editor like vi or nano, or a simple text editor such as TextEdit or Atom.{quote}
          The steps described in this howto to install php is incomplete and won't make sense to the supported platforms - maybe in MacOs only - and shouldn't be here.

          h2. The paths are non standard
          According to the [Requirements & System Configuration|https://doc.ez.no/pages/viewpage.action?pageId=31429536] page, the recommended setups should be Debian, Ubuntu or RHEL / CentOS.

          The paths on the page are not the ones used in neither of these systems and should be fixed.

          {code}sudo vi /private/etc/apache2/httpd.conf
          sudo vi /private/etc/apache2/users/ez1.lh.conf{code}

          * In the first case, the path should probably be {{/etc/apache2/apache2.conf}} in Debian and {{/etc/httpd/httpd.conf}} in CentOS.
          * In the second one, {{/etc/apache2/apache2.conf}} in Debian and {{/etc/httpd/conf.d}} in CentOS.

          ^MacOS is not a supported platform and should not be used in documentation^

          h2. Apache setup
          {quote}b. Uncomment and modify the following lines:
          {code}LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
          LoadModule rewrite_module libexec/apache2/mod_rewrite.so{code}{quote}
          This does not make sense since Debian, for example, uses *a2enmod* to enable modules. But the main reason is we shouldn't explain how to enable modules, we should just list them as required on the [Requirements|https://doc.ez.no/pages/viewpage.action?pageId=31429536] page.

          h2. Hosts file configuration
          {quote}This step is allows you to use ez1.lh as an address to access running Platform from a web browser. You can substitute the address with the address you intend to use to access your installation (remember to change it in all other command on this page as well):{quote}
          This is something only makes sense in a development environment. It should be removed from the official documentation.

          h2. Composer should not be installed this way
          {code}mv composer.phar /usr/local/bin/composer{code}
          I remember some time ago we - engineering - talked about having the documentation with a composer alias or the full command {{php -d memory_limit=-1 composer.phar}} and the decision was stay with the full command to have a safe standard. This rule should be kept here and in the documentation.

          h2. Install additional requirements for eZ Platform
          {code}cd /usr/lib/php
          sudo php install-pear-nozlib.phar{code}
          * If the steps described here are mandatory, why they are not described in the [INSTALL.md|https://github.com/ezsystems/ezplatform/blob/master/INSTALL.md] file? I think they are not.
          * The steps does not explain how to obtain the {{install-pear-nozlib.phar}} file and so they won't work.

          {code}apt-get install icu4c
          sudo pecl install intl{code}
          * Again, we shouldn't explain how to install packages but list them as required on the [Requirements|https://doc.ez.no/pages/viewpage.action?pageId=31429536]. Besides, I think icu4c won't even exist in Debian and CentOs.

          h2. Install eZ Platform
          {quote}git clone https://github.com/ezsystems/ezplatform.git {quote}
          The steps listed here are very different from the ones described in the [INSTALL.md|https://github.com/ezsystems/ezplatform/blob/master/INSTALL.md] file what is very confusing, specially for customers since the [Manual Installation Guides|https://doc.ez.no/display/DEVELOPER/Manual+Installation+Guides] page instructs them to download the software from {{share.ez.no/downloads/downloads}}.

          h2. Modify virtual host file based on dev environment
          * The steps listed here should follow the lead on [Apache 2.2 / 2.4 configuration|https://github.com/ezsystems/ezplatform/blob/master/doc/apache2/Readme.md].
          * Listing a virtual host file here may result in compatibility and maintenance problems. Instead, we should link it to the [vhost.template|https://github.com/ezsystems/ezplatform/blob/master/doc/apache2/vhost.template] on Github.

          h2. Install required dependencies using Composer
          {code}composer install{code}
          Again the full form should be used.

          h2. Invalid permissions
          {code}sudo chmod +a "_www allow delete,write,append,file_inherit,directory_inherit" app/{cache,logs,config} web{code}
          Afaik, these are MacOS only - see [Mac OS Man page|https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/chmod.1.html] - and shouldn't be here.

          h2. Optional steps
          Some of these steps does not make sense to Debian or CentOS.
          There are some inconsistencies on the [Installation Guide for Unix-based Systems|https://doc.ez.no/display/DEVELOPER/Installation+Guide+for+Unix-based+Systems] documentation page.

          h2. MySQL install section does not make sense
          {quote}Download from the official MySQL webpage is strongly recommended.{quote}

          Why we *strongly recommend* customers to download MySQL from their website instead using the standard packages of their distributions with
          which our software was tested?

          Besides the testing, it's important to remember that we *must provide* support and reproduce customer bugs and as closer their environment is to testing and support environments, the better.

          h2. PHP set up incomplete
          {quote}This step requires the modification of two files: Apache2 configuration file and php.ini.
          These files can be edited using a terminal editor like vi or nano, or a simple text editor such as TextEdit or Atom.{quote}
          The steps described in this section are incomplete and won't make sense to the supported platforms - maybe in MacOs only - and shouldn't be here.

          h2. The paths are non standard
          According to the [Requirements & System Configuration|https://doc.ez.no/pages/viewpage.action?pageId=31429536] page, the recommended setups should be Debian, Ubuntu or RHEL / CentOS.

          The paths on the page are not the ones used in neither of these systems and should be fixed.

          {code}sudo vi /private/etc/apache2/httpd.conf
          sudo vi /private/etc/apache2/users/ez1.lh.conf{code}

          * In the first case, the path should probably be {{/etc/apache2/apache2.conf}} in Debian and {{/etc/httpd/httpd.conf}} in CentOS.
          * In the second one, {{/etc/apache2/apache2.conf}} in Debian and {{/etc/httpd/conf.d}} in CentOS.

          ^MacOS is not a supported platform and should not be used in documentation^

          h2. Apache setup
          {quote}b. Uncomment and modify the following lines:
          {code}LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
          LoadModule rewrite_module libexec/apache2/mod_rewrite.so{code}{quote}
          This does not make sense since Debian, for example, uses *a2enmod* to enable modules. But the main reason is we shouldn't explain how to enable modules, we should just list them as required on the [Requirements|https://doc.ez.no/pages/viewpage.action?pageId=31429536] page.

          h2. Hosts file configuration
          {quote}This step is allows you to use ez1.lh as an address to access running Platform from a web browser. You can substitute the address with the address you intend to use to access your installation (remember to change it in all other command on this page as well):{quote}
          This is something only makes sense in a development environment. It should be removed from the official documentation.

          h2. Composer should not be installed this way
          {code}mv composer.phar /usr/local/bin/composer{code}
          I remember some time ago we - engineering - talked about having the documentation with a composer alias or the full command {{php -d memory_limit=-1 composer.phar}} and the decision was stay with the full command to have a safe standard. This rule should be kept here and in the documentation.

          h2. Install additional requirements for eZ Platform
          {code}cd /usr/lib/php
          sudo php install-pear-nozlib.phar{code}
          * If the steps described here are mandatory, why they are not described in the [INSTALL.md|https://github.com/ezsystems/ezplatform/blob/master/INSTALL.md] file? I think they are not.
          * The steps does not explain how to obtain the {{install-pear-nozlib.phar}} file and so they won't work.

          {code}apt-get install icu4c
          sudo pecl install intl{code}
          * Again, we shouldn't explain how to install packages but list them as required on the [Requirements|https://doc.ez.no/pages/viewpage.action?pageId=31429536]. Besides, I think icu4c won't even exist in Debian and CentOs.

          h2. Install eZ Platform
          {quote}git clone https://github.com/ezsystems/ezplatform.git {quote}
          The steps listed here are very different from the ones described in the [INSTALL.md|https://github.com/ezsystems/ezplatform/blob/master/INSTALL.md] file what is very confusing, specially for customers since the [Manual Installation Guides|https://doc.ez.no/display/DEVELOPER/Manual+Installation+Guides] page instructs them to download the software from {{share.ez.no/downloads/downloads}}.

          h2. Modify virtual host file based on dev environment
          * The steps listed here should follow the lead on [Apache 2.2 / 2.4 configuration|https://github.com/ezsystems/ezplatform/blob/master/doc/apache2/Readme.md].
          * Listing a virtual host file here may result in compatibility and maintenance problems. Instead, we should link it to the [vhost.template|https://github.com/ezsystems/ezplatform/blob/master/doc/apache2/vhost.template] on Github.

          h2. Install required dependencies using Composer
          {code}composer install{code}
          Again the full form should be used.

          h2. Invalid permissions
          {code}sudo chmod +a "_www allow delete,write,append,file_inherit,directory_inherit" app/{cache,logs,config} web{code}
          Afaik, these are MacOS only - see [Mac OS Man page|https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/chmod.1.html] - and shouldn't be here.

          h2. Optional steps
          Some of these steps does not make sense to Debian or CentOS.
          Eduardo Fernandes (Inactive) made changes -
          Description There are some inconsistencies on the [Installation Guide for Unix-based Systems|https://doc.ez.no/display/DEVELOPER/Installation+Guide+for+Unix-based+Systems] documentation page.

          h2. MySQL install section does not make sense
          {quote}Download from the official MySQL webpage is strongly recommended.{quote}

          Why we *strongly recommend* customers to download MySQL from their website instead using the standard packages of their distributions with
          which our software was tested?

          Besides the testing, it's important to remember that we *must provide* support and reproduce customer bugs and as closer their environment is to testing and support environments, the better.

          h2. PHP set up incomplete
          {quote}This step requires the modification of two files: Apache2 configuration file and php.ini.
          These files can be edited using a terminal editor like vi or nano, or a simple text editor such as TextEdit or Atom.{quote}
          The steps described in this section are incomplete and won't make sense to the supported platforms - maybe in MacOs only - and shouldn't be here.

          h2. The paths are non standard
          According to the [Requirements & System Configuration|https://doc.ez.no/pages/viewpage.action?pageId=31429536] page, the recommended setups should be Debian, Ubuntu or RHEL / CentOS.

          The paths on the page are not the ones used in neither of these systems and should be fixed.

          {code}sudo vi /private/etc/apache2/httpd.conf
          sudo vi /private/etc/apache2/users/ez1.lh.conf{code}

          * In the first case, the path should probably be {{/etc/apache2/apache2.conf}} in Debian and {{/etc/httpd/httpd.conf}} in CentOS.
          * In the second one, {{/etc/apache2/apache2.conf}} in Debian and {{/etc/httpd/conf.d}} in CentOS.

          ^MacOS is not a supported platform and should not be used in documentation^

          h2. Apache setup
          {quote}b. Uncomment and modify the following lines:
          {code}LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
          LoadModule rewrite_module libexec/apache2/mod_rewrite.so{code}{quote}
          This does not make sense since Debian, for example, uses *a2enmod* to enable modules. But the main reason is we shouldn't explain how to enable modules, we should just list them as required on the [Requirements|https://doc.ez.no/pages/viewpage.action?pageId=31429536] page.

          h2. Hosts file configuration
          {quote}This step is allows you to use ez1.lh as an address to access running Platform from a web browser. You can substitute the address with the address you intend to use to access your installation (remember to change it in all other command on this page as well):{quote}
          This is something only makes sense in a development environment. It should be removed from the official documentation.

          h2. Composer should not be installed this way
          {code}mv composer.phar /usr/local/bin/composer{code}
          I remember some time ago we - engineering - talked about having the documentation with a composer alias or the full command {{php -d memory_limit=-1 composer.phar}} and the decision was stay with the full command to have a safe standard. This rule should be kept here and in the documentation.

          h2. Install additional requirements for eZ Platform
          {code}cd /usr/lib/php
          sudo php install-pear-nozlib.phar{code}
          * If the steps described here are mandatory, why they are not described in the [INSTALL.md|https://github.com/ezsystems/ezplatform/blob/master/INSTALL.md] file? I think they are not.
          * The steps does not explain how to obtain the {{install-pear-nozlib.phar}} file and so they won't work.

          {code}apt-get install icu4c
          sudo pecl install intl{code}
          * Again, we shouldn't explain how to install packages but list them as required on the [Requirements|https://doc.ez.no/pages/viewpage.action?pageId=31429536]. Besides, I think icu4c won't even exist in Debian and CentOs.

          h2. Install eZ Platform
          {quote}git clone https://github.com/ezsystems/ezplatform.git {quote}
          The steps listed here are very different from the ones described in the [INSTALL.md|https://github.com/ezsystems/ezplatform/blob/master/INSTALL.md] file what is very confusing, specially for customers since the [Manual Installation Guides|https://doc.ez.no/display/DEVELOPER/Manual+Installation+Guides] page instructs them to download the software from {{share.ez.no/downloads/downloads}}.

          h2. Modify virtual host file based on dev environment
          * The steps listed here should follow the lead on [Apache 2.2 / 2.4 configuration|https://github.com/ezsystems/ezplatform/blob/master/doc/apache2/Readme.md].
          * Listing a virtual host file here may result in compatibility and maintenance problems. Instead, we should link it to the [vhost.template|https://github.com/ezsystems/ezplatform/blob/master/doc/apache2/vhost.template] on Github.

          h2. Install required dependencies using Composer
          {code}composer install{code}
          Again the full form should be used.

          h2. Invalid permissions
          {code}sudo chmod +a "_www allow delete,write,append,file_inherit,directory_inherit" app/{cache,logs,config} web{code}
          Afaik, these are MacOS only - see [Mac OS Man page|https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/chmod.1.html] - and shouldn't be here.

          h2. Optional steps
          Some of these steps does not make sense to Debian or CentOS.
          There are some inconsistencies on the [Installation Guide for Unix-based Systems|https://doc.ez.no/display/DEVELOPER/Installation+Guide+for+Unix-based+Systems] documentation page.

          h4. MySQL install section does not make sense
          {quote}Download from the official MySQL webpage is strongly recommended.{quote}

          Why we *strongly recommend* customers to download MySQL from their website instead using the standard packages of their distributions with
          which our software was tested?

          Besides the testing, it's important to remember that we *must provide* support and reproduce customer bugs and as closer their environment is to testing and support environments, the better.

          h4. PHP set up incomplete
          {quote}This step requires the modification of two files: Apache2 configuration file and php.ini.
          These files can be edited using a terminal editor like vi or nano, or a simple text editor such as TextEdit or Atom.{quote}
          The steps described in this howto to install php is incomplete and won't make sense to the supported platforms - maybe in MacOs only - and shouldn't be here.

          h4. The paths are non standard
          According to the [Requirements & System Configuration|https://doc.ez.no/pages/viewpage.action?pageId=31429536] page, the recommended setups should be Debian, Ubuntu or RHEL / CentOS.

          The paths on the page are not the ones used in neither of these systems and should be fixed.

          {code}sudo vi /private/etc/apache2/httpd.conf
          sudo vi /private/etc/apache2/users/ez1.lh.conf{code}

          * In the first case, the path should probably be {{/etc/apache2/apache2.conf}} in Debian and {{/etc/httpd/httpd.conf}} in CentOS.
          * In the second one, {{/etc/apache2/apache2.conf}} in Debian and {{/etc/httpd/conf.d}} in CentOS.

          ^MacOS is not a supported platform and should not be used in documentation^

          h4. Apache setup
          {quote}b. Uncomment and modify the following lines:
          {code}LoadModule vhost_alias_module libexec/apache2/mod_vhost_alias.so
          LoadModule rewrite_module libexec/apache2/mod_rewrite.so{code}{quote}
          This does not make sense since Debian, for example, uses *a2enmod* to enable modules. But the main reason is we shouldn't explain how to enable modules, we should just list them as required on the [Requirements|https://doc.ez.no/pages/viewpage.action?pageId=31429536] page.

          h4. Hosts file configuration
          {quote}This step is allows you to use ez1.lh as an address to access running Platform from a web browser. You can substitute the address with the address you intend to use to access your installation (remember to change it in all other command on this page as well):{quote}
          This is something only makes sense in a development environment. It should be removed from the official documentation.

          h4. Composer should not be installed this way
          {code}mv composer.phar /usr/local/bin/composer{code}
          I remember some time ago we - engineering - talked about having the documentation with a composer alias or the full command {{php -d memory_limit=-1 composer.phar}} and the decision was stay with the full command to have a safe standard. This rule should be kept here and in the documentation.

          h4. Install additional requirements for eZ Platform
          {code}cd /usr/lib/php
          sudo php install-pear-nozlib.phar{code}
          * If the steps described here are mandatory, why they are not described in the [INSTALL.md|https://github.com/ezsystems/ezplatform/blob/master/INSTALL.md] file? I think they are not.
          * The steps does not explain how to obtain the {{install-pear-nozlib.phar}} file and so they won't work.

          {code}apt-get install icu4c
          sudo pecl install intl{code}
          * Again, we shouldn't explain how to install packages but list them as required on the [Requirements|https://doc.ez.no/pages/viewpage.action?pageId=31429536]. Besides, I think icu4c won't even exist in Debian and CentOs.

          h4. Install eZ Platform
          {quote}git clone https://github.com/ezsystems/ezplatform.git {quote}
          The steps listed here are very different from the ones described in the [INSTALL.md|https://github.com/ezsystems/ezplatform/blob/master/INSTALL.md] file what is very confusing, specially for customers since the [Manual Installation Guides|https://doc.ez.no/display/DEVELOPER/Manual+Installation+Guides] page instructs them to download the software from {{share.ez.no/downloads/downloads}}.

          h4. Modify virtual host file based on dev environment
          * The steps listed here should follow the lead on [Apache 2.2 / 2.4 configuration|https://github.com/ezsystems/ezplatform/blob/master/doc/apache2/Readme.md].
          * Listing a virtual host file here may result in compatibility and maintenance problems. Instead, we should link it to the [vhost.template|https://github.com/ezsystems/ezplatform/blob/master/doc/apache2/vhost.template] on Github.

          h4. Install required dependencies using Composer
          {code}composer install{code}
          Again the full form should be used.

          h4. Invalid permissions
          {code}sudo chmod +a "_www allow delete,write,append,file_inherit,directory_inherit" app/{cache,logs,config} web{code}
          Afaik, these are MacOS only - see [Mac OS Man page|https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/chmod.1.html] - and shouldn't be here.

          h4. Optional steps
          Some of these steps does not make sense to Debian or CentOS.
          Eduardo Fernandes (Inactive) made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          Eduardo Fernandes (Inactive) made changes -
          Summary Documentation: Installation Guide must be reviewed Documentation: UNIX-based installation Guide must be reviewed
          Paulo Nunes (Inactive) made changes -
          Link This issue relates to EZP-25823 [ EZP-25823 ]
          Michał Maciej Kusztelak (Inactive) made changes -
          Link This issue relates to EZS-806 [ EZS-806 ]
          David Christian Liedle (Inactive) made changes -
          Assignee David Christian Liedle [ david.liedle@ez.no ]
          André Rømcke made changes -
          Status Confirmed [ 10037 ] Backlog [ 10000 ]
          André Rømcke made changes -
          Status Backlog [ 10000 ] Development [ 3 ]
          Assignee David Christian Liedle [ david.liedle@ez.no ] André Rømcke [ andre.romcke@ez.no ]
          André Rømcke made changes -
          Status Development [ 3 ] Development Review done [ 10028 ]
          Assignee André Rømcke [ andre.romcke@ez.no ]
          Sarah Haïm-Lubczanski (Inactive) made changes -
          Assignee David Christian Liedle [ david.liedle@ez.no ]
          David Christian Liedle (Inactive) made changes -
          Status Development Review done [ 10028 ] Documentation Review done [ 10011 ]
          Assignee David Christian Liedle [ david.liedle@ez.no ]
          Rui Silva (Inactive) made changes -
          Status Documentation Review done [ 10011 ] QA [ 10008 ]
          Rui Silva (Inactive) made changes -
          Assignee Rui Silva [ rui.silva@ez.no ]
          Status QA [ 10008 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Sarah Haïm-Lubczanski (Inactive) made changes -
          Link This issue relates to EZP-26085 [ EZP-26085 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 99257 ] EZEE Development Workflow [ 125775 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Eduardo Fernandes (Inactive)
            • Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: