Jira still can't rename a field per project so I built the app to fix it(and yes, it works with JQL)

[Mohin Pasha]

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:

1. Would this actually solve a real problem on your instance?
2. 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.

[Matt Doar _Adaptavist_]

Interesting. Doesn't the aliasField function need to know which Jira space/project to refer to, so it can map the alias name to the underlying custom field name? I guess the JQL could have a "project =" clause at the beginning

Also, could the same mechanism be used for system fields?

[Mohin Pasha]

Good point. Since aliases are project-scoped, the recommended usage is to include the project in the JQL to provide the necessary context for alias resolution. For example:

issue in aliasField("Go-Live Date", ">= now()") AND project = "My Kanban Space"

Regarding system fields, the same mechanism is used for both system and custom fields. However, there are currently some limitations with system fields. While many system fields are supported, aliasField() does not work correctly for a few of them. Additionally, the Due date field is one of them and cannot be renamed on the Issue View and Transition screens due to the known Atlassian platform issue FRGE-1897. These are known platform and implementation limitations that I plan to investigate and address in future iterations of the project.