<h3 dir="auto">Apache Airflow version</h3>
<p dir="auto">2.3.2 (latest released)</p>
<h3 dir="auto">What happened</h3>
<p dir="auto">Grid view for a Task Group (renders incorrectly)<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/80706212/172630971-12ca3955-cc3c-4c47-ad56-2a7643551353.png"><img width="865" alt="image" src="https://user-images.githubusercontent.com/80706212/172630971-12ca3955-cc3c-4c47-ad56-2a7643551353.png" style="max-width: 100%;"></a></p>
<p dir="auto">Graph View for same Task Group (renders correctly)<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/80706212/172630694-cf29ef79-6b67-45e8-b15b-3196366f274c.png"><img width="1168" alt="image" src="https://user-images.githubusercontent.com/80706212/172630694-cf29ef79-6b67-45e8-b15b-3196366f274c.png" style="max-width: 100%;"></a></p>
<ol dir="auto">
<li>
<p dir="auto">All historic DAG Runs for the task group are marked as "up_for_reschedule" because the <em>current</em> DAG Run task group has a "up_for_reschedule" task in it. It is observable in this screenshot that this is incorrect for all except the current DAG Run. The same was happening for "failed" statuses or "up_for_retry"</p>
</li>
<li>
<p dir="auto">Also there is a visual issue in rendering the bottom two task names of the task group - their names are cut off - <code class="notranslate">process_XXX_files_and_upload</code> turned into <code class="notranslate">s_XXX_files_and_upload</code>.</p>
</li>
</ol>
<h3 dir="auto">What you think should happen instead</h3>
<ol dir="auto">
<li>Task group should report status based on it's DAG Run</li>
<li>Task names should render correctly</li>
</ol>
<h3 dir="auto">How to reproduce</h3>
<p dir="auto">(assumption) Have a DAG with a Task Group and historical task runs in <code class="notranslate">2.3.2</code></p>
<h3 dir="auto">Operating System</h3>
<p dir="auto">Debian/Docker</p>
<h3 dir="auto">Versions of Apache Airflow Providers</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Deployment</h3>
<p dir="auto">Astronomer</p>
<h3 dir="auto">Deployment details</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Anything else</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Are you willing to submit PR?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> Yes I am willing to submit a PR!</li>
</ul>
<h3 dir="auto">Code of Conduct</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I agree to follow this project's <a href="https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md">Code of Conduct</a></li>
</ul>
<h3 dir="auto">Apache Airflow version</h3>
<p dir="auto">2.3.2 (latest released)</p>
<h3 dir="auto">What happened</h3>
<p dir="auto">I updated to 2.3.2 today and while i love the new additions to the task groups ui i am getting weird behavior with their statuses. The previous run task groups status is changing to whatever the current run status is:</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/43684949/172405342-690dce8f-f3ca-4e5f-b4ed-67356e35e87a.png"><img src="https://user-images.githubusercontent.com/43684949/172405342-690dce8f-f3ca-4e5f-b4ed-67356e35e87a.png" alt="image" style="max-width: 100%;"></a></p>
<p dir="auto">As you can see the top task group finished completely in the previous run but is now showing deferred because the most recent has that status. Same with the one below, it is showing running even though it is actually complete. I can post a video of all this happening real time if needed.</p>
<h3 dir="auto">What you think should happen instead</h3>
<p dir="auto">They should show their own status, not the most recent one.</p>
<h3 dir="auto">How to reproduce</h3>
<p dir="auto">All of my DAGs are doing it, so seems like you just need to have multiple runs on a DAG with task groups to reproduce.</p>
<h3 dir="auto">Operating System</h3>
<p dir="auto">Windows 10</p>
<h3 dir="auto">Versions of Apache Airflow Providers</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Deployment</h3>
<p dir="auto">Astronomer</p>
<h3 dir="auto">Deployment details</h3>
<p dir="auto">Currently developing locally, will not be pushing this version to deployment until this is resolved.</p>
<h3 dir="auto">Anything else</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Are you willing to submit PR?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> Yes I am willing to submit a PR!</li>
</ul>
<h3 dir="auto">Code of Conduct</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I agree to follow this project's <a href="https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md">Code of Conduct</a></li>
</ul>