Project on revenue forecast #70
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Introduced a new `ProjectSummary` class to encapsulate project-related metrics and fees. - Updated the `compute_forecast` function to aggregate and summarize data by projects, similar to existing client and case logic. - Enhanced the `CaseSummary` class to include a list of projects associated with each case, improving data visibility. - Implemented a method to retrieve cases by Everhour project name, facilitating better project-case relationships. These changes improve the forecasting capabilities by integrating project-level insights, enhancing the overall analytics framework and user experience within the revenue forecasting feature.
- Added support for forecasting by projects in the GraphQL schema, introducing new types `ForecastByProjectEntry` and `ForecastConsultingByProjectEntry`. - Updated existing types to include project-related metrics, improving data granularity and analysis capabilities. - Enhanced the overall analytics framework by integrating project-level insights, aligning with previous enhancements for clients and sponsors. These changes improve the forecasting capabilities by incorporating project-level data, further enriching the user experience within the revenue forecasting feature.
- Implemented expandable rows for projects within the Revenue Forecast page, allowing users to toggle visibility of associated project metrics. - Updated rendering logic to display detailed project data beneath respective cases when expanded, improving data accessibility and user engagement. - Enhanced GraphQL queries to include project-level data across all forecasting categories (consulting, consultingPre, handsOn, squad), enriching the overall analytics framework. - Improved user interaction with a button for expanding/collapsing project rows, providing a more detailed view of project-level insights. These changes enhance the user experience by offering a comprehensive and interactive view of revenue forecasting, integrating project-level data for better analysis.
- Introduced helper functions for rendering table cells, headers, and rows, enhancing code readability and maintainability. - Updated the rendering logic to utilize these helper functions, streamlining the display of financial data and improving overall UI consistency. - Enhanced user interaction by maintaining expandable rows for clients and sponsors, ensuring a comprehensive view of associated data. - Improved the display of totals at the bottom of the table, ensuring clarity in financial summaries. These changes enhance the user experience by providing a cleaner, more interactive interface for revenue forecasting, while also improving code structure.
- Updated rendering logic to support an additional row depth for project details, allowing users to view associated projects beneath cases. - Modified the expandable row functionality to include project-level insights, enhancing data visibility and user engagement. - Improved the conditional rendering of links and text based on row depth, providing a clearer distinction between different data levels. These changes enhance the user experience by offering a more comprehensive and interactive view of revenue forecasting, integrating deeper project-level data for better analysis.
- Modified the CaseSummary class to retrieve the slug from the associated case object instead of generating it from the case title. - This change enhances data integrity by ensuring the slug accurately reflects the case's unique identifier, improving consistency in revenue tracking. These updates contribute to a more reliable and cohesive data structure within the revenue tracking framework.
- Modified the link for case items in the Revenue Forecast page to point to the new `/about-us/cases/` path, ensuring accurate navigation to case details. - This change improves the user experience by providing a clearer and more consistent URL structure for accessing case information.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.