Example of the use case behind this idea:

If a customer have set up multiple legal entities in D365 FnO and sales order confirmations shall be generated from each legal entity, normally one batch job per legal entity is set up. One of main reasons to set up one batch job per legal entity is to have the ability to change the batch job header status to 'Withhold' or any other status if required.

However, to get a better structure and a better overview in the batch job list and to reduce the amount of batch job headers for the same batch class, it would be very beneficial to work with one batch job header with multiple batch tasks (this can be done already today of course, but with limitations).

A prerequisite to accomplish this and to make it work E2E would be to have the ability to change the status on a single batch task. For example, if a sales order confirmation in legal entity 1 must be paused but the confirmations in legal entity 2 and 3 can continue to process.