"Start Date," "Go-Live Date," "Launch Date" — same field, three duplicate copies. Built a Forge app

Mohin Pasha

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:

• Aliases any field, scoped to one project — the field, its ID, and its data never change
• The new name shows up automatically on issue create, view, and transition screens, no per-screen setup needed
• You can search by the alias directly in JQL, like issue in aliasField("Go-Live Date", ">= 2026-06-01","KAN"), instead of needing to know the field's real name
• One dashboard shows every alias across every project in one place
• Every change is logged — who aliased what, and when

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.

Install it here: https://developer.atlassian.com/console/install/7a289919-273f-41f6-95d4-fb434c8d38e6?signature=AYABeLsrO5S31OXed%2FvieOvXFiQAAAADAAdhd3Mta21zAEthcm46YXdzOmttczp1cy13ZXN0LTI6NzA5NTg3ODM1MjQzOmtleS83MDVlZDY3MC1mNTdjLTQxYjUtOWY5Yi1lM2YyZGNjMTQ2ZTcAuAECAQB4IOp8r3eKNYw8z2v%2FEq3%2FfvrZguoGsXpNSaDveR%2FF%2Fo0B%2BCh%2BwVD34wv%2F2ECtXyO0XAAAAH4wfAYJKoZIhvcNAQcGoG8wbQIBADBoBgkqhkiG9w0BBwEwHgYJYIZIAWUDBAEuMBEEDEc4%2Bnea%2F2aLI5SkWgIBEIA7%2FLDksST03Cmo8sFQrME5Ii0VE3rPzm%2B1S%2FhibhGedyz2qES%2Bx5%2BVHLg3Pzv07bMnWKMhC5AwqZ7gfs0AB2F3cy1rbXMAS2Fybjphd3M6a21zOmV1LXdlc3QtMTo3MDk1ODc4MzUyNDM6a2V5LzQ2MzBjZTZiLTAwYzMtNGRlMi04NzdiLTYyN2UyMDYwZTVjYwC4AQICAHijmwVTMt6Oj3F%2B0%2B0cVrojrS8yZ9ktpdfDxqPMSIkvHAF%2BhRrb%2FKJcUxRgmiFX4Oj7AAAAfjB8BgkqhkiG9w0BBwagbzBtAgEAMGgGCSqGSIb3DQEHATAeBglghkgBZQMEAS4wEQQM4IARciyZU%2BtjTxfHAgEQgDvqgp57A325yBBBNXNa%2FZNSBfPMWRF%2B4AhTQHjh03VPjwx9%2BK5kgRpwkNVuHwIkhbdPgUjXmqgzlWY5nAAHYXdzLWttcwBLYXJuOmF3czprbXM6dXMtZWFzdC0xOjcwOTU4NzgzNTI0MzprZXkvNmMxMjBiYTAtNGNkNS00OTg1LWI4MmUtNDBhMDQ5NTJjYzU3ALgBAgIAeLKa7Dfn9BgbXaQmJGrkKztjV4vrreTkqr7wGwhqIYs5AdiIWTUnyia%2FSYgAEoKmU0UAAAB%2BMHwGCSqGSIb3DQEHBqBvMG0CAQAwaAYJKoZIhvcNAQcBMB4GCWCGSAFlAwQBLjARBAxEW7lL01xhwfU7TRwCARCAO3SbuKksYIcnAtvkgigduNUMfnR8vbYjbqWvz7o5VnxeVtpILdP6XjqGY%2Fe530CBYM2SOpIue9iQUgr9AgAAAAAMAAAQAAAAAAAAAAAAAAAAAPMkrM8JRsDtkciLhg5PecL%2F%2F%2F%2F%2FAAAAAQAAAAAAAAAAAAAAAQAAADIQiay%2BrgNiJfC%2FIRIrugLTeq5q%2BmQL3Xh7lwgohLdvlojwjW42m5RT0a87czTi9OAOOCKad%2Fr7dFj3bhdEWoKqBeM%3D&product=jira

 

Gor Greyan

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! 🙌