Fix forecast #95
Merged
Fix forecast #95
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
- Updated the `compute_pre_contracted_revenue_tracking` function to set the fee to zero based on project creation and due dates, improving revenue calculation accuracy. - Refactored the `from_base_instance` method in the `Project` model to use `model_dump()` for better data handling. - Modified the `fetch_all_projects_json` method in the `Everhour` class to streamline project fetching, while maintaining the original `fetch_all_projects` method for backward compatibility. - Adjusted the `due_on` field in the `Task` model to use an alias, enhancing data consistency and clarity. These changes improve the overall functionality and accuracy of revenue tracking and project management within the application.
- Reduced the task fetch limit from 10,000 to 250 in the `fetch_project_tasks` method to optimize performance and prevent excessive data retrieval. - Changed the `searchInClosed` parameter from a boolean to a string in the `_search_tasks_json` method for compatibility with the API. - Updated the `due_on` field in the `Task` model to set a default value of `None`, enhancing data handling and consistency. These changes enhance the efficiency and reliability of task management within the Everhour integration.
- Updated the `compute_pre_contracted_revenue_tracking` function to ensure accurate fee calculations based on project due dates, accommodating various date formats. - Added logic in the `CasesRepository` to set due dates for archived tracker projects, improving project management consistency. - Introduced the `enforce_due_on` method in the `TimeTracker` class to automatically assign due dates from tasks, enhancing task management reliability. - Implemented a new `find_project_due_on` method to streamline due date retrieval for projects, improving overall functionality. These changes improve the accuracy and reliability of project and revenue tracking within the application.
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.