Skip to end of banner
Go to start of banner

E2F - Known issues and limitations

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Feature related fields are displayed as field ID in JQL search

When you include Feature related fields to your JQL search, they are displayed as field name but when you select them, they are displayed as field ID.

This limitation is caused by Atlassian, and relates to this ticket with Atlassian. As soon as Atlassian resolves the ticket, we will be able to display field names in the search field as well. The good news is that we managed to make it so that epic is not displayed. 

What you searchWhat Jira displays


Is this possible to configure different namings for different Jira projects?

We have been investigating this very feature (pun not intended), however, at the moment this is not possible.

The issue with this is that for some of the translations we have to rely on Jira functionality, that is custom field and issue type translation is done by Jira itself. And it is applied globally to all screens across the Jira instance, including all projects and boards.

In this context, if we attempt to apply translations by project we will need to get rid of or work around the base Jira functionality that we rely on and create an approach which will modify the UI values of the html by javascript functions and will be tied by the UI itself. And the potential solution could still be unstable and unportable across Jira versions.

That being said, we are working on the alternatives at the moment, because offering something unstable and unreliable to our users is the last thing we want to do.

  • No labels