fix(dar): format Data Access Request expiry as a date in the task tab - #30873
fix(dar): format Data Access Request expiry as a date in the task tab#30873anuj-kumary wants to merge 2 commits into
Conversation
The Activity Feed / Task tab renders the DAR payload via TaskPayloadSchemaFields using DAR_FIELD_FORMATTERS, which formatted `duration` but not `expirationDate` — so the expiry showed as a raw epoch number (e.g. 1786699421850) while the DAR detail drawer showed it as a friendly date. Add an `expirationDate` formatter that reuses the shared `formatDate` util so both surfaces are consistent. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
❌ PR checklist incompleteThis PR cannot be merged until the following are addressed on its linked issue:
The fields live on the linked issue in the Shipping project (open the issue → right sidebar → Projects). After you set them, re-run this check (or push a commit) — issue/project changes do not re-trigger it automatically. Maintainers can bypass this check by adding the |
|
Hi there 👋 Thanks for your contribution! The OpenMetadata team will review the PR shortly! Once it has been labeled as Let us know if you need any help! |
Code Review ✅ ApprovedFormats Data Access Request expiry values as friendly dates in the task tab using the existing shared formatDate utility. No issues found. OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar | Powered by Gitar — free for open source |
|
Hi there 👋 Thanks for your contribution! The OpenMetadata team will review the PR shortly! Once it has been labeled as Let us know if you need any help! |
|
|



What & why
On the entity Activity Feed & Tasks tab, a Data Access Request's Expiration Date was shown as a raw epoch number (e.g.
1786699421850), while the DAR detail drawer showed the same value as a friendly date. The task tab renders the DAR payload generically viaTaskPayloadSchemaFields, applying per-fieldDAR_FIELD_FORMATTERS— that map formatteddurationbut had no entry forexpirationDate, so the number fell through unformatted.How
Add an
expirationDateentry toDAR_FIELD_FORMATTERSthat reuses the existing sharedformatDateutil (the same one the DAR detail drawer uses), so both surfaces render the expiry consistently.Issue -

Testing
🤖 Generated with Claude Code