How to Move a Job on the Gantt Chart in EDGEBIC

To move a job on the Gantt chart in EDGEBIC by User Solutions, open the Job View Gantt tab and drag the bar to its new slot. The bar takes the overridden color and the Save Changes button lights up, but nothing is written until you commit. It is a deliberate, deferred model: drag as many bars as you like, review them, then save them together or discard the lot. And it is override-and-warn, so the move happens whether or not the new slot has capacity.

The wider drag-and-drop workflow, including how the colors read, is in drag and drop rescheduling in EDGEBIC. This is the single move.

Before You Start

Step 1: Open the Gantt

Open the Job View tab and switch to the Gantt tab. Each operation is a colored appointment bar on its work center's row. When neighboring jobs crowd the bar you want, shade or hide the rest first, which changes the display and not the plan.

Step 2: Drag the Bar

Drag the bar horizontally to a new start time. As you drop it:

• the bar takes the overridden color,
• the change is held in memory, not written to the database,
• the Save Changes button becomes enabled,
• if the new start is before the job's target start, a warning appears in the status bar.

This is override-and-warn. The move is not checked against capacity. If the target slot is already full, the drag still lands there, and it is on you to confirm the slot can take the work. When you want placement within capacity, run a reschedule instead, described in how to reschedule safely.

Step 3: Save or Discard

Two buttons close the loop.

Discard works only before you save. Once committed, a drag is recorded as actual dates and there is no discard: you drag the bar back and save again, or clear the actuals it wrote and reschedule.

Understand What a Saved Drag Writes

A saved time drag writes the operation's actual start and end to the dropped position and leaves the scheduled start and end at the engine's computed values. That split is intentional. Actual dates say where the job really is; scheduled dates say what the engine planned. The gap between them is what lets the Gantt color an overridden bar differently from a rescheduled one, and it is why the next reschedule treats your drag exactly like a logged actual: it will not move a step that now carries an actual start.

Moving a Job to a Different Machine

Dragging a bar vertically to a different resource row changes its work center, and that is a two-phase commit. Saving stages the swap; the actual routing change is applied on the next reschedule run, which also records it in the audit trail. So the sequence is drag to the new row, save, then reschedule the job. Discarding the pending changes before that reschedule removes the staged swap as well.

Two guardrails apply. A capacity-request job configured to disallow work-center replacement reverts the resource change on drop, allowing only a time shift. And if other operations on the same job already have pending replacements, a status-bar warning appears.

What Changes When You Save

How to Check It Worked

Read the bar's color: an applied override is visually distinct from an engine-computed slot, and Gantt colors and labels decodes every state. Open the operation's row in the Job View grid and confirm the actual start and end match where you dropped the bar, while the scheduled dates are unchanged. For an audit-grade check, open Job Audit: a date-override event carries the old and new start and end, which how to see who changed a schedule covers.

Common Mistakes

• Trusting the slot has capacity because the drag allowed it. Override-and-warn allows any drop. The feasibility check is yours.
• Expecting the scheduled dates to move. They do not. A saved drag writes actuals, which is why the bar reads as an override rather than a fresh plan.
• Expecting a work-center drag to take effect on save. It stages. Reschedule to apply it.
• Dragging a bar and then rescheduling without saving. Unsaved drags live only on your screen. Save or discard before you reschedule, or the run ignores them.
• Hand-placing the whole plant. A Gantt full of overrides is a plant where feasibility is unknown. Drag the few that matter, then let a reschedule tidy the rest.

Next Steps

If the drag was meant to correct a date rather than override a slot, how to correct a wrong actual date is the cleaner path. To read the result against the plan, see planned versus actual on the EDGEBIC Gantt. When a drag made a job jump further than expected on the next run, why did my job jump after a reschedule explains it.

Every task in this library is indexed on the EDGEBIC how-to hub. Bring a schedule with one job in the wrong place to a demo of EDGEBIC and we will drag it, save it, and reschedule around it.