Automation for Jira
4 January 2024, 22:27
• Jira Internal Users
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).
Automation for Jira
2 January 2024, 19:33
• Jira Internal Users
This issue was planned to be delivered until 2024-01-22. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-22, 2024-01-02
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
Automation for Jira
2 January 2024, 15:10
• Jira Internal Users
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
Automation for Jira
2 January 2024, 15:10
• Jira Internal Users
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
Automation for Jira
2 January 2024, 13:36
• Jira Internal Users
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp,douglascoimbra.
Automation for Jira
2 January 2024, 13:36
• Jira Internal Users
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
fix(billing): billing duplicated requests; home chart tooltip
Automation for Jira
28 December 2023, 19:51
• Jira Internal Users
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
Automation for Jira
28 December 2023, 15:27
• Jira Internal Users
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
fix(billing): billing duplicated requests; home chart tooltip
Ingo Wagner
28 December 2023, 01:39
• Jira Internal Users
Automation for Jira
11 December 2023, 20:39
• Jira Internal Users
@Andre Pasold , @Pedro Buzzi , @Ingo Wagner ,
This issue was planned to be delivered until 2024-01-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
Done
Details
Priority
Medium
Assignee
Ingo Wagner
Reporter
Andre Pasold
Labels
PLANNED
Due Date
22 January 2024
Fix versions
CAPL_3.98
Components
BILLING | ACCOUNT_MANAGER
Created
30 November 2023, 11:29
Updated
23 January 2024, 11:16
More fields
Original estimate
None
Time tracking
None
Affects versions
None
Rest of custom fields
None
Created: 30 November 2023, 15:29Updated:
23 January 2024, 15:16
This issue was automatically transitioned to WAITING DEPLOY, as its linked QA regression issue has just reached WAITING DEPLOY status (PR was just merged into master branch in Github).
@Andre Pasold ,
@Geny Isam Hamud Herrera , @Ingo Wagner , @Andre Pasold , @Carlos Affonso Wagner , @Douglas Coimbra Lopes
This issue was planned to be delivered until 2024-01-22. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-22, 2024-01-02
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to REGRESSION, as its PR was just merged into qa branch in Github.
This issue was automatically transitioned to TESTED & MERGED, as its PR was just merged into develop branch in Github. PR Approved by andregp,douglascoimbra.
Github user douglascoimbra has just approved a PR (added as Shard Assignee in this Jira issue).
fix(billing): billing duplicated requests; home chart tooltip
This issue was automatically transitioned to QA REVIEW, as its PR was just approved in Github.
This issue was automatically transitioned to REVIEW, as its PR (not DRAFT and not WIP) was just created in Github.
fix(billing): billing duplicated requests; home chart tooltip
@Andre Pasold ,
@Pedro Buzzi , @Ingo Wagner ,
This issue was planned to be delivered until 2024-01-01. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-01-01
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.