Version 2

    Summary

    You may see instances where the names of profile fields do not show up or show up as blank in various places throughout the Jive application.  This may happen in the user registration page, editing a user profile, and when filtering people by profile fields.

     

    This issue happens when a profile field is configured without any text translations for the profile field name. Bug JIVE-42193 has since been resolved in Jive 7.0.2, 8, and Cloud, which prevents profile fields from being saved without at least one translation.  Despite this bug fix, this does not mean that older profile fields edited prior to the bug fix may not exhibit this behavior.

     

    Issue Details

    • Bug ID: JIVE-42193
    • Bug Summary: Not having Language Display names set causes sort by filter to post blank for sort name
    • Affected Versions: 7.0.0
    • Fixed: 7.0.2 & Jive Cloud

     

    Identifying the Problem

    Versions

    The document has been verified against Jive 7, 8 and Jive Cloud

     

    Symptoms

    You may see that profile field names are blank in several areas of Jive:

    • Create new account
    • Profile Edit page
    • Profile Edit page in Admin Console

     

    Screen Shot 2015-08-03 at 2.49.43 PM.png

    Screen Shot 2015-08-03 at 2.50.25 PM.png

     

    You may also see that profile field names are blank when filtering users in the People page in Jive:

     

    Screen Shot 2015-08-03 at 3.06.19 PM.png

     

    Cause

    This issue with blank profile fields can happen when a profile field is created in Jive that does not have a translation created for the profile field name:

    Screen+Shot+2015-07-16+at+6.49.10+AM.png

     

    Workaround

    To address this issue you will need to go to Admin Console: People > Settings > Profile Settings, and then update the profile field so that there is a translation for one of the profile fields.

     

    Screen+Shot+2015-07-16+at+6.49.10+AM.png

     

    Bug JIVE-42193 has been addressed so that profile fields can no longer be created without having at least one translation. This does mean that profile fields created before this bug fix may be susceptible to this bug if there wasn't a translation created at the time of the field being created.