Unify task insertion logic using Store service to remove redundancy #2255
Description
Is your feature request related to a problem? Please describe.
Currently, adding a new task can involve interacting with various components such as Project, Section, or Task objects directly, depending on the context. This has created code duplication and redundancy in the task insertion logic, especially when using features like Quick Add.
Describe the solution you'd like
Refactor and unify the task insertion process by always using the Store service as the single point of entry for creating tasks, regardless of whether the insertion is from Quick Add, a project, or another context. This will simplify the logic, reduce code duplication, and make future maintenance easier.
Describe alternatives you've considered
Maintaining the current approach, but this continues to create and propagate redundant code paths and makes it harder to update or extend task insertion logic consistently.
Additional context
Unifying task creation through the Store service will help streamline the codebase and make new enhancements easier to implement in the future.