The answer is YES. Currently the display value of all entities can be changed, including projects, programmes, employees and all project related entities e.g. tasks.
Where are the display values shown?
For illustration purposes, let’s use the issue list page as an example. When accessing the issue list page you will notice the project list and employee lists (for the Contact Person and Issue Owner) within the List Criteria section. When clicking on those drop-down lists it will show the display value for the projects and employees respectively.
On the bottom of the issue list page, the display value of the project and the employee lists is also shown.
You will also see the display value on move pages delete pages for all project related entities, and the sort order for the tasks entity.
In the below example we have used the “Sprint” entity for illustration purposes. Let’s look at the display value when sprint items are moved or deleted:
You will notice that the display value for the sprints shows the start date of the week, the sprint key, the team responsible for the sprint, as well as the status of the sprint. The display value has been changed specifically for this entity.
The task entity is the only entity that also has a “sort order” option and the display value will therefore also appear on the task sort order edit page as shown below:
Please note that when custom entities are used, the default display value is set to always show the first text field within the custom entity, for example if you use the benefits entity, the display value will be the title of the benefit.
Lastly the display value is also shown in the history records of the respective items.
Will the display value also appear on the time entries and approval pages?
The Approvals and Time Entries entities reference the project entity as well as all other project related entities, for example Issues, Tasks, Risks etc.
The display value of projects and project related entities is shown for all entries added to the time entry page as well as in all drop-downs when adding items manually as shown in the screenshot above.
On the approvals page, the display value of the relevant entities is also shown.
Examples of display values that you could change
If we use the employees as an example, you will notice that the default display value for employees is: “Surname, Name”. Your employee Joe Bloggs, will therefore by default be displayed on all employee lists as “Bloggs, Joe”. In the below example the display names for employees was changed from Surname, Name to Name Surname. So "Bloggs, Joe" can be changed to show as "Joe Bloggs".
After the display value has been changed, you will notice that the employee will also show as: “Joe Bloggs”, when accessing reports where an employee list is used, for example the Issue Report, which shows the employees that the issues are assigned to.
Firstly, on the report criteria page, the dropdowns will show the display values of the items, if the dropdown is either a combo or entity list (i.e. it shows the individual items rather than just filters. In most cases we only use combos or lists for project, programme and employee fields but it is also possible to show a combo or entity list for project related entities. In this case, the dropdown will show the display values for those entities.
In the screenshot below, the only criteria is a Sprint entity list which is a custom entity and for which the display value has been customised to show the start date, the sprint key, the team responsible for the sprint, as well as the status of the sprint.
Display values will also appear in the report itself, e.g. if you have customised the display value of the employee entity as described above, everywhere that an employee field appears, it will be in the customised format.
How do I change the display value on the instance?
The display value can be changed with the assistance from the PPO Support team. Just log a support call and they will gladly assist.
- When changing your display value ensure the change is simple and does not cause your instance to be slower, because of all the SQL expressions being used. In essence do not over complicate your display values.