Skip to content

Conversation

tirkarthi
Copy link
Contributor

Closes #50904

@tirkarthi tirkarthi requested a review from dstandish May 22, 2025 15:31
@boring-cyborg boring-cyborg bot added the area:UI Related to UI/UX. For Frontend Developers. label May 22, 2025
Copy link
Member

@pierrejeambrun pierrejeambrun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good, thanks

@pierrejeambrun pierrejeambrun added the backport-to-v3-0-test Mark PR with this label to backport to v3-0-test branch label May 22, 2025
@pierrejeambrun pierrejeambrun merged commit f8c8200 into apache:main May 22, 2025
44 checks passed
github-actions bot pushed a commit that referenced this pull request May 22, 2025
…th schedule. (#50969)

(cherry picked from commit f8c8200)

Co-authored-by: Karthikeyan Singaravelan <[email protected]>
Copy link

Backport successfully created: v3-0-test

Status Branch Result
v3-0-test PR Link

kaxil pushed a commit that referenced this pull request May 22, 2025
…th schedule. (#50969) (#50970)

(cherry picked from commit f8c8200)

Co-authored-by: Karthikeyan Singaravelan <[email protected]>
@jscheffl
Copy link
Contributor

Mhm, I just see this change and... actually I dis-like it. I undrstand that people seeking for (the new cool feature to backfill as advertised) and can not see it if no schedule.

BUT: The new UI uses a lot more whitespace and when using the trigger form as modal a lot of screen space is occupied for a selection that is actually not a benefit if you just want to trigger.
In our environment 80% of DAGs are without schedule. For our users it might rather be confusing having this option when they never thought of backfill.

Could we make this somehow configurable? In my view it just clutters the UI when no backfill possible.

@pierrejeambrun
Copy link
Member

pierrejeambrun commented May 23, 2025

Later on the UI will also handle the permissions, which means that this button will most likely disappear again if users do not have permissions to create backfill. Maybe that could be a workaround => Don't give user backfill permissions if you don't want them to see the disabled button. (But that's 3.1.0+ unfortunately).

kaxil pushed a commit that referenced this pull request Jun 3, 2025
…th schedule. (#50969) (#50970)

(cherry picked from commit f8c8200)

Co-authored-by: Karthikeyan Singaravelan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:UI Related to UI/UX. For Frontend Developers. backport-to-v3-0-test Mark PR with this label to backport to v3-0-test branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When dag has no schedule, still show backfill button but grayed out
3 participants