[
https://issues.apache.org/jira/browse/AIRFLOW-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827358#comment-16827358
]
ASF GitHub Bot commented on AIRFLOW-4418:
-----------------------------------------
ahuynh3 commented on pull request #5193: [AIRFLOW-4418] Add clear failed only
button to DAG modal
URL: https://github.com/apache/airflow/pull/5193
Make sure you have checked _all_ steps below.
### Jira
- [x] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
- In case you are proposing a fundamental code change, you need to create
an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Description
- [x] Here are some details about my PR, including screenshots of any UI
changes:
Add a button to **Clear Only Failed** to DAG modal:
This button functions similarly to the existing **Clear** button, but only
considers failed tasks. This may be useful if you have tasks that have failed,
and want to rerun them with a single click while keeping successful tasks as is.
Consider the following example DAG:
Hitting the **Clear Only Failed** button should recursively clear all failed
tasks:
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Just adding a route that is similar to an existing route (/dagrun_clear) and
a button to the UI that ultimately calls the clear method of the DAG class,
which is already tested.
### Commits
- [x] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
- If you implement backwards incompatible changes, please leave a note in
the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so
we can assign it to a appropriate release
### Code Quality
- [x] Passes `flake8`
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add flag on Dag Modal to clear only the failed tasks
> ----------------------------------------------------
>
> Key: AIRFLOW-4418
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4418
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Sreejith Madhavan
> Priority: Minor
> Labels: usability
> Fix For: 1.10.4, 2.0.0
>
>
> Add flag on UI (Modal for the Dag) to clear only the failed tasks. This
> should recursively clear only the failed tasks in the dag (unlike the current
> behavior to include success tasks being cleared as well)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
