Every Jira admin has done this: created 3 duplicate "Date" fields because 3 teams couldn't agree on what to call it — Start Date, Go-Live Date, Launch Date — all storing the exact same thing, just to make everyone happy.
Jira's had this gap forever. Atlassian's never fixed it. So I built the fix myself.
Field Aliaser — give any field a different display name per project, with zero duplicate fields. The underlying field, its ID, its data — completely untouched. Only the label changes.
🔹 Set it once — alias shows up automatically on Create, View, and Transition screens, no manual screen wiring
🔹 Search by the alias, not the cryptic real name:
issue in aliasField("Go-Live Date", ">= 2026-06-01")🔹 100% Forge-native — runs entirely on Atlassian's infrastructure, no external servers, no data leaving your site
I checked the Marketplace before building this — nothing does per-project field renaming on the actual issue screens. (The closest thing only relabels fields on the JSM customer portal — different problem entirely.)
It's working end-to-end right now.
Before Field Alias:
After Field Alias:
Two questions for you:
- Would this actually solve a real problem on your instance?
- Anyone willing to break it on a test site and tell me what falls over?
Drop a comment below — I'd rather hear "this is useless because X" now than after launch.
