Skip to content
Snippets Groups Projects
  1. Jun 13, 2024
  2. Jun 08, 2024
  3. Jun 04, 2024
  4. Jun 01, 2024
  5. May 28, 2024
  6. May 27, 2024
  7. May 22, 2024
  8. May 21, 2024
  9. May 08, 2024
  10. May 07, 2024
  11. May 06, 2024
    • Wes Appler's avatar
      Visibility fixes for partners that are also applicants (#3893) · 3b513347
      Wes Appler authored
      Fixes #3892. This solution was a bit unruly (especially ugly after
      linting) but it seemed like the logical approach without refactoring the
      whole `visibility_for` to be a normal method rather than a class method.
      This fix evaluates if the partner/reviewer is the author of the source
      submission first before evaluating the their role. The reviewer role was
      also lumped in here because even though I know we advise against a
      reviewer also being an applicant, it still could happen without
      oversight.
      
      I tried to keep the code as clean as I could and reuse QuerySets, but
      let me know if y'all see any way I can optimize!
  12. May 04, 2024
  13. May 01, 2024
    • Saurabh Kumar's avatar
    • Saurabh Kumar's avatar
      Refractor primary nav and dashboard, hide projects info if not enabled (#3898) · ab4e5ecf
      Saurabh Kumar authored
      Also, refractor and allow for importing permission functions from
      anywhere and not just limit to be imported from the
      `hypha.users.decorators` module
      
      This PR also doesn't display project info on the dashboard if the
      projects is not enabled
      
      For the stats block at the top of the dashboard, if the projects is not
      abled displays the count of flagged submissions and the count of
      previously reviewed submissions
      
      Simplify the nav generator logic. 
      ab4e5ecf
    • Fredrik Jonsson's avatar
      Project Reports as stream field forms (#3611) · 3463cc10
      Fredrik Jonsson authored
      
      With `PROJECTS_ENABLED = True`, Project Report Forms may now be
      created in Wagtail Admin and associated with a Fund.
      
      Project reports use the form configured in Wagtail admin. To add or
      edit a report form, use `Projects -> Report Forms`. To bind a report
      form to a given Fund, use `Apply -> Funds`, set `Project Report Form`.
      
      When projects are enabled, a project shows the Reports in various
      project interfaces. A new project report will use the current fields
      from the Project Report Form associated with the Fund from which the
      Submission/Application was granted. An existing report, when edited,
      will use the original fields at the time that report was first filed.
      This behavior appears consistent with at least one other similar form.
      
      Thanks to Frank Duncan for the "View" functionality in
      hypha/apply/projects/templates/application_projects/report_detail.html
      and NonFileFormFieldsBlockFactory for tests that don't need files
      as well as re-adding the url for project file lookup by id.
      
      Co-authored-by: default avatarFrank Duncan <frankduncan@opentechstrategies.com>
      
      ---------
      
      Co-authored-by: default avatarJesse Bickel <bickelj@gmail.com>
      Co-authored-by: default avatarFrank Duncan <frankduncan@opentechstrategies.com>
      3463cc10
  14. Apr 30, 2024
    • Saurabh Kumar's avatar
      Fix alignment of text in the plain-text emails (#3903) · 587c6c7a
      Saurabh Kumar authored
      Due to djhtml the emails templates where formatted with indendation.
      That lead to alignment also being present in the plain-text emails.
      
      This was an unintentional behaviour that this PR fixes by adding {#
      fmt:off #} markers in the email templates so djhtml won't format them
      587c6c7a
  15. Apr 25, 2024
  16. Apr 23, 2024
  17. Apr 17, 2024
  18. Apr 12, 2024
Loading