Skip to content
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

Fix: 1745 milestone values persist #1814

Merged
merged 9 commits into from
Aug 1, 2023

Conversation

Sepehr-Sobhani
Copy link
Contributor

@Sepehr-Sobhani Sepehr-Sobhani changed the title Fix 1745 milestone values persist Fix: 1745 milestone values persist Jul 20, 2023
Copy link
Collaborator

@BCerki BCerki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work!

A couple things:

  1. This PR removes the calculated values from the payments table, but I wonder if it should remove the payment record entirely?
  2. I'm seeing a funky diff for holdback:
    image
    This happened when I created a new project, created a General Milestone, and filled out everything. Then in my revision I changed the type to a Reporting Milestone

@Sepehr-Sobhani Sepehr-Sobhani force-pushed the 1745-milestone-values-persist branch 2 times, most recently from fb61175 to 725f58d Compare July 26, 2023 18:53
Copy link
Collaborator

@BCerki BCerki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work!

I found another redundant arrow that I added to your bug card: https://app.zenhub.com/workspaces/climate-action-secretariat-60ca4121764d710011481ca2/issues/gh/bcgov/cas-cif/1822

@Sepehr-Sobhani Sepehr-Sobhani merged commit 9c0e504 into develop Aug 1, 2023
16 checks passed
@Sepehr-Sobhani Sepehr-Sobhani deleted the 1745-milestone-values-persist branch August 1, 2023 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants