feature/FOUR-18130: [FALL] Case Detail Page

[pmPaulis]

Issue & Reproduction Steps

The updated Case Detail Page addresses the core pain points of fragmented information, improve tracking, and visibility. By introducing a unified and comprehensive view, it enhances efficiency, organization, tracking, and productivity in Case management. (In Flight Process Map, Case Timeline, Cancel Behavior, Counters)

PRD
Case Detail Page

FIGMA
Fall 2024

Stories

• As a user I want to see the information of cases when I click the Case Tab
• As a user I want to see the information of Case Tab, the counters should display information dispalying counters
• As a Designer I want to have the option to see the list of My Requests
• As a User I want to see the correct information of dates in the Cases Tables
• As a user, I want to see all the tasks related to the case, when I open a case
• As a user I want to see the list of completed Tasks
• As a user I want to see the history of all the Request of a Case
• As a user I want to see the comments of all the Requests
• As a user I want to have an option to see all the Request detail in a Tab
• As a User I want to see the inflight process map of a Case
• As a user I should be able to Cancel a Request and more than one request if is the case.
• As a User I should be able to see a new Design for Counters in Case Table
• As a user I want to see the number of Request that corresponds to the opened Case
• As a User I want to see a breadcrumb related to cases

How to Test

Go to Cases menu

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-18130

PR Related

https://github.com/ProcessMaker/package-savedsearch/pull/469

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

ci:next
ci:deploy
ci:package-savedsearch:feature/FOUR-18130

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net

[tokensPM]

QA server K8S was successfully deployed https://ci-7352ae7ac5.engk8s.processmaker.net