Task actions UI for individual mapped instances#23127
Merged
Merged
Conversation
boring-cyborg
Bot
added
area:UI
ashb
force-pushed
the
mapped-instance-actions
branch
from
a70282d to
b77aa9a
Compare
ashb
approved these changes
Apr 21, 2022
jedcunningham
approved these changes
Apr 21, 2022
jedcunningham
added
the
changelog:skip
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update Grid, Graph and Gantt to be able to perform all task actions on each individual mapped task instance.
In Grid and Graph, you can be on a mapped task summary page. And so you can perform bulk actions affecting all mapped tasks (This is how it was already working).
In Grid, you can select any number of mapped instances in the table and fire off a single request to act upon just those instances.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragement file, named
{pr_number}.significant.rst, in newsfragments.