You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the diffs page, a diff should only be shown if the user changed a form. In the project summary report section, we see "Project Summary Report not updated" if there's been no change. It's not inaccurate, but it's inconsistent.
I think the CollapsibleFormWidget may be displaying the wrong component for the Project Summary Report (the conditionality in app/components/Form/ProjectSummaryReportFormSummary.tsx looks ok)
Probability (how likely the bug is to happen, scored from 1-5): 3
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5): 1
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
create a general revision for an IA project
navigate to the summary page
see a message under the project summary header
Screenshots:
Additional information:
OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional context
The text was updated successfully, but these errors were encountered:
Describe the Bug:
On the diffs page, a diff should only be shown if the user changed a form. In the project summary report section, we see "Project Summary Report not updated" if there's been no change. It's not inaccurate, but it's inconsistent.
I think the CollapsibleFormWidget may be displaying the wrong component for the Project Summary Report (the conditionality in
app/components/Form/ProjectSummaryReportFormSummary.tsx
looks ok)Probability (how likely the bug is to happen, scored from 1-5): 3
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5): 1
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Screenshots:
Additional information:
The text was updated successfully, but these errors were encountered: