Skip to content

DREF Superticket 2.0 BUGS #1784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
10 tasks
anamariaescobar opened this issue Apr 9, 2025 · 0 comments
Open
10 tasks

DREF Superticket 2.0 BUGS #1784

anamariaescobar opened this issue Apr 9, 2025 · 0 comments
Labels
type: bug Something isn't working

Comments

@anamariaescobar
Copy link

Page URL

https://go.ifrc.org/dref-applications/new

Environment

Production

Browser

Chrome

Steps to Reproduce the Issue

Some functions of the DREF Application are not working as expected, this ticket will describe all of those.

@udaynwa @samshara @tovari

Expected Behavior

  • Automatic email should be trigger once a DREF has been shared with a new person. The user added can access the DREF, but no email is being triggered. This used to work.
  • Under Event details > Description of the Event, despite the maximum of 2 photos limitation, it’s possible to upload more photos. Adding more photos does not prevent the user from continuing and saving the request. Change the description to add maximum 4 photo, and block the system so it only allows 4 photos maximum. Add a characters limit to the caption of 80 characters.
  • Under Actions/Needs Section and Targeting strategy Add a description to the files to updated documents with the type of files:
  • Assessment report: pdf, docx, pptx, xlsx.
  • Financial report file types: pdf.
  • Remove the error involving the following field (we removed the field of targeted population from Operation overview a while ago from the Application, and I have requested to remove it from Ops Update and Final Report in DREF Superticket 2.0 (New features) #1695 )

Image

  • Under Operation > Objective and Strategy Rationale, for “Overall objective of the operation” and “Operation strategy rationale”, move the description under the title so it doesn’t disappear when you start typing? We expect users to follow the hint/template, but at the same time, it’s not visible the moment they start writing. [enhancement].
  • IMPORT TEMPLATE: For the sake of user-friendliness, can we make sure all titles are well visible? Currently, in some cases, the text seems to have an additional row on top, pushing the text down. [enhancement] This is the case under Event Detail, Actions Needs, and Operation tabs.
  • IMPORT TEMPLATE: Under Operation tab, Total Targeted Population, can we add under the explanation/hint box “If 0, leave the box empty” (or allow 0)?

Image

  • If the DREF was uploaded from the import file, it looks like the Priority Actions under Planed Interventions, don’t get standard bullet points.

Image

  • Can the gender disaggregation provided under Operation > Update on intervention be reflected in the ops update export [and final report]?
  • [ ]When creating an ops update, if no amount is added to the “Additional allocation requested" field, the “total allocation” field remains empty. The “total allocation” should be from the start equal to field “Budget Allocated so far”, it should never start empty. Another idea is to default the "additional allocation requested" to be defaulted to 0 so the user has to change it and not leave it empty.

Image

  • For Loan type: In Operation Section, bring back the field to add the total allocation in CHF

Actual Behavior

Actual behavior is describe on the box above.

Priority

Medium (Affects functionality, but there is a workaround)

Additional Context (Optional)

No response

@anamariaescobar anamariaescobar added the type: bug Something isn't working label Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant