The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • "Start Date," "Go-Live Date," "Launch Date" — same field, three duplicate copies. Built a Forge app

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

Mohin Pasha
August 12, 2026

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.

field-aliaser-before-after.png

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%2BVHLg3Pzv...


field-aliaser-jql-search.pngfield-aliaser-admin-config.png

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 12, 2026

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

Mohin Pasha
August 12, 2026

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.

Like Gor Greyan likes this
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 12, 2026

Hi @Mohin Pasha

Sure, will try it and will provide feedback, Mohin.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events