Selected dag trigger logical date is different from the logical date that is sent to the backend
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 472
Description
### Apache Airflow version
3.1.7
### If "Other Airflow 3 version" selected, which one?
_No response_
### What happened?
When I trigger a new dag, the selected logical date does not match the logical date sent to the backend.
### What you think should happen instead?
The logical date selected in the UI should be exactly the same as the one sent to the backend to avoid confusion. The format of the logical date in the date picker should also match the format of the rest of the UI.
### How to reproduce
Set the timezone in the UI to UTC+1.
Trigger a dag manually and provide a logical date.
### Operating System
Windows 11
### Versions of Apache Airflow Providers
_No response_
### Deployment
Other Docker-based deployment
### Deployment details
_No response_
### Anything else?
_No response_
### Are you willing to submit 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)
Contributor guide
Assessment
This issue has not been assessed yet.