1. 30 Nov, 2020 1 commit
  2. 07 Aug, 2020 2 commits
    • Gabriel Monnerat's avatar
      erp5_officejs_support_request_ui_test: Add test to make sure we have all... · 68081daf
      Gabriel Monnerat authored
      erp5_officejs_support_request_ui_test: Add test to make sure we have all expected actions to access support request web site
      
      * Check if each portal_type has the expected view action
      * add test to cover all possible attachments in a Support Request
      68081daf
    • Gabriel Monnerat's avatar
      erp5_officejs_support_request_ui: New gadget to generate RSS Link and remove it from dashboard · 4705a2fe
      Gabriel Monnerat authored
      Having a big "Generate RSS" button on the front page is strange, because the front page button are for common use cases that users are supposed to execute a lot.
      
      For example, makes sense to have a "Submit new Support Request" button, because users are using this app to submit support requests, but generating RSS is very exceptional action, so we wanted to remove it from the front page.
      
      Also, we changed:
      - change the generate_rss_link action in Support Request Module, to directly call SupportRequestModule_generateRSSLinkUrl.py instead of the form.
      - change SupportRequestModule_generateRSSLinkUrl to display the form at the end.
      - Use Base_renderForm like for erp5_crm
      - Put the RSS url in the REQUEST
      - change the gadget field configuration to use the value from the REQUEST (if not found, put None)
      - change the gadget implementation to display the URL in an html5 string field  + a button
      4705a2fe
  3. 19 Mar, 2019 1 commit
  4. 13 Nov, 2018 3 commits
  5. 01 Nov, 2018 3 commits
  6. 23 Oct, 2018 1 commit
    • Jérome Perrin's avatar
      officejs_support_request_ui: Take into account preferred SR use · 65a57d30
      Jérome Perrin authored
      Only services whose use is included in the preferred SR use are
      allowed when openning a support request.
      
      We still filter the services according to supply lines applicable for
      the selected project, but allow all SR services when project does not
      define supplies.
      
      Another user visible change is that test we no longer select a random
      service, it must be a user decision (eventhough one possible
      sophistication could be to select the service when there's only one).
      Update test accordingly.
      
      Also use relative URL for service, not just the service ID (this is API
      breaking change, but the javascript part should not have this cached)
      65a57d30
  7. 11 Oct, 2018 4 commits