Every Jira admin has hit this at some point: three teams want the same field called three different things, so instead of sharing one field, you end up with three near-identical copies just to keep everyone happy. Over time your instance gets cluttered with duplicates, and reporting quietly fragments across them — nobody notices until someone tries to build a report across projects and realizes the data's split three ways.
I built Field Aliaser to actually fix that instead of working around it. One real field, a different display name per project, and nothing else about it changes.
Here's what it actually does:
issue in aliasField("Go-Live Date", ">= 2026-06-01","KAN"), instead of needing to know the field's real name
Try to break it, and tell me honestly what's confusing, missing, or wrong — not just "looks cool." Comment below or DM me too if you'd rather talk it through first.
Hi @Mohin Pasha
Nice work, Mohin! This looks like a really useful approach, especially for larger Jira instances where duplicate fields with different names can quickly become a reporting and administration headache. Thanks for sharing this with the Community! 🙌
Thanks, @Gor Greyan ! Really glad it's useful.
If you'd like, I'd love for you to try it on a real project and tell me what works, what's confusing, or what you'd want added. Feedback from someone who's actually dealt with this problem would help a lot.
No pressure though — happy to have you along whenever works for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.