farhan-labib09 opened a new issue, #45858:
URL: https://github.com/apache/airflow/issues/45858

   ### Description
   
   
   ## Repository Version
   Apache Airflow version 2.10.4
   ## Search terms / keywords
   dynamic task grouping, execution date, task dependencies, workflow 
optimization
   ## Description
   Currently, Airflow does not support dynamic task grouping based on execution 
dates. Users are unable to programmatically group tasks according to the 
specific execution date of a DAG run. This enhancement would enable workflows 
to have better task dependency management and reduce the complexity of DAG 
definitions.
   ## What happened (current behavior)
   In the current Airflow version, users have to manually define task 
dependencies or use complex logic to group tasks dynamically. This results in 
more rigid and harder-to-manage DAGs, especially in cases where workflows need 
to adapt to different execution dates.
   ## What do you think should happen instead (expected behavior)
   We propose adding the ability to dynamically group tasks based on the 
execution date. This would allow users to create more flexible and adaptable 
DAGs by grouping tasks automatically according to the specific date of 
execution, reducing boilerplate code and making the workflow easier to maintain.
   
   
   
   
   ### Use case/motivation
   
   ## Use case and motivating examples (for feature requests)
   This feature would benefit users working with large, time-sensitive 
workflows where tasks need to be grouped based on the specific run date. For 
example:
   - Financial reports that must be generated for specific dates.
   - ETL processes that need different data sources based on the execution date.
   
   ### Related issues
   
   n/a
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to