Skip to content

Wrong status shown for billing account #1412

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

Closed
jmgasper opened this issue Sep 1, 2022 · 1 comment
Closed

Wrong status shown for billing account #1412

jmgasper opened this issue Sep 1, 2022 · 1 comment
Milestone

Comments

@jmgasper
Copy link
Collaborator

jmgasper commented Sep 1, 2022

Seen in production:

Problem

Today for the Timeline Wall project the billing account was showing IN_REVIEW

It looks like the Connect Project was In Review, but the Billing Account was active.

Screenshot_6

Solution

The BA should only show two status - "ACTIVE" or "INACTIVE".

jmgasper added a commit that referenced this issue Sep 2, 2022
#1412

1. A "project" contains "status" field , this status field can be "active"/"in_review"

2. A "project" also has a billingAccount mapped.

3. Application makes a GET call with billingAccount id to get billingAccount details. and response of it is this screenshot https://imgur.com/cU3s4yU

4. response has "active" boolean field and enddate field which is correctly utilised in reducer code to set the flag "isBillingAccountExpired". check this screenshot https://imgur.com/l5nyxbt

5. now this "isBillingAccountExpired" flag is used like this. check screenshot https://imgur.com/mjDhbAF

6. when "isBillingAccountExpired" is true, we show hardcoded "INACTIVE" which is correct.

7. but when "isBillingAccountExpired" is false , we show "status" field of "project" which is wrong, because we need to show whether billingAccount is active or not.

8. hence "status" field of project can be active/inReview , thats why u see "IN_REVIEW" in UI,

9. hence my solution/approach is that flag "isBillingAccountExpired" is already there which clearly indicates active/inactive, hence i hardcoded "ACTIVE" in code because it is obvious.
@jmgasper jmgasper closed this as completed Sep 2, 2022
jmgasper added a commit that referenced this issue Oct 10, 2022
#1412

1. A "project" contains "status" field , this status field can be "active"/"in_review"

2. A "project" also has a billingAccount mapped.

3. Application makes a GET call with billingAccount id to get billingAccount details. and response of it is this screenshot https://imgur.com/cU3s4yU

4. response has "active" boolean field and enddate field which is correctly utilised in reducer code to set the flag "isBillingAccountExpired". check this screenshot https://imgur.com/l5nyxbt

5. now this "isBillingAccountExpired" flag is used like this. check screenshot https://imgur.com/mjDhbAF

6. when "isBillingAccountExpired" is true, we show hardcoded "INACTIVE" which is correct.

7. but when "isBillingAccountExpired" is false , we show "status" field of "project" which is wrong, because we need to show whether billingAccount is active or not.

8. hence "status" field of project can be active/inReview , thats why u see "IN_REVIEW" in UI,

9. hence my solution/approach is that flag "isBillingAccountExpired" is already there which clearly indicates active/inactive, hence i hardcoded "ACTIVE" in code because it is obvious.

# Conflicts:
#	src/components/ChallengesComponent/ChallengeList/index.js
@jmgasper jmgasper added this to the 0.16.0 milestone Oct 11, 2022
@sdgun
Copy link

sdgun commented Oct 11, 2022

Verified in Prod with available projects.

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

No branches or pull requests

2 participants