Revanth14 opened a new pull request, #68194:
URL: https://github.com/apache/airflow/pull/68194

   The Task Instances table only let you reach a mapped task instance through 
the **Start Date** column. When an instance had not started yet 
(`queued`/`scheduled`), Start Date was empty, so the row had no clickable 
target and those instances were hard to reach — you had to go up to the run and 
click through the task list instead.
   
   The **Map Index** cell now links to the mapped task instance details page 
for mapped rows (`map_index >= 0`), built from the row's own task instance 
identity. Because Map Index is always present (even before the task starts), 
queued/scheduled mapped instances are now reachable directly. Non-mapped rows 
(`map_index == -1`) stay plain text, and the link renders in every context the 
table is used in (mapped-task view, run task list, and the Browse view).
   
   closes: #68177
   
   ## Manual verification
   - Reproduced with a mapped task whose queued mapped instances had no start 
date.
   - Before: Map Index was plain text.
   - After: Map Index linked to the mapped task instance details page.
   
   ### Before
   <img width="1512" height="830" alt="before_fix" 
src="https://github.com/user-attachments/assets/2d59e4e4-8d20-4716-a4c8-642461300c5d";
 />
   
   ### After
   <img width="1510" height="737" alt="after_fix1" 
src="https://github.com/user-attachments/assets/85505aa8-bc96-48db-851c-44bf6ed9469a";
 />
   <img width="1511" height="626" alt="after_fix2" 
src="https://github.com/user-attachments/assets/b3aa6cd6-ac86-45e4-a44b-1501b07a2fb7";
 />
   
   
   ## Tests
   - `pnpm vitest run src/pages/TaskInstances/TaskInstances.test.tsx` 
   - `pnpm eslint --quiet src/pages/TaskInstances/TaskInstances.tsx 
src/pages/TaskInstances/TaskInstances.test.tsx`
   - `pnpm tsc -p tsconfig.app.json --noEmit`
   
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — OpenAI Codex (GPT-5)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to