Show which costs are being shared with other Billing accounts
Description
PRDE - Story default text according to the team DoR (Definition of Ready)
01 - STAKEHOLDER (PERSON THAT CAN VALIDATE AND ANSWER QUESTIONS):
02 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):
Recently we made some updates on billing to allow sharing carol apps and tenants costs between two or more Billing accounts.
03 - GOAL (DESCRIBE THE PROPOSED SOLUTION):
We need to show on costs information that a specific cost is a part of the total.
04 - WHO CAN USE THIS FEATURE (USER ROLES):
05 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
06 - ACCEPTANCE CRITERIA:
- Add an icon with the column Total Cost, only on Tenant tab (for account managers)
- Show tooltip on mouse over: “The cost from this Tenant is shared between [N] Billing accounts. Total cost is [R$N]
- On exported invoice (csv) add a column beside tenant_id called cost_shared_by_billing_accounts and inform quantity of billing accounts (1, 2, 3…)
Activity
Show:
Details
Priority
HighAssignee
Ingo Wagner
Reporter
Robson Thanael Poffo
Labels
CAROL_BACKLOG_REVIEWPLANNED
Due Date
15 April 2024
Fix versions
CAPL_4.02
Components
BILLING | ACCOUNT_MANAGER
Created
27 February 2024, 17:47
Updated
16 April 2024, 15:21
More fields
Created: 27 February 2024, 21:47
Updated:
16 April 2024, 20:21
@Robson Thanael Poffo ,
@Jonathan Willian Moraes , @Ingo Wagner ,
This issue was planned to be delivered until 2024-04-15. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-04-15, 2024-03-25
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to WAITING DEPLOY, as its PR was just merged into master branch in Github.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
refactor:
CAPL-5574 Done show tenant cost share in endpoint that returns cost by tenant
This issue was automatically transitioned to IN PROGRESS, as its branch was just created in Github.
This issue was automatically transitioned to IN PROGRESS, as its branch was just created in Github.
@Robson Thanael Poffo ,
@Pedro Buzzi ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-03-25. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-03-25
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.