Hi @Arun Kumar - Dagster currently has the constraint that, if you're using a partitioned job, each job run corresponds to a single partition. This means that the Dagster partitioned jobs can't model "this single job run backfilled 30 different partitions".
If you want that flexibility, you could write a job that accepts a time range as config and a schedule that runs it daily with config for that day. To run "backfills", people could launch the job from the Launchpad (what used to be called the Playground) and supply the time range they want to backfill as config. However, the job wouldn't be able to take advantage of the Partitions UI.
We'd ultimately like to be able to address the pattern you brought up about with asset partitions - a single job run would be able to fill in multiple partitions for an asset, and you'd be able to go to the asset page to view a matrix that shows the status of each of the asset's partitions.