Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-64958

Method getCustomFieldObjectsByName() doesn't accept the right input parameter

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 7.3.3, 7.3.4
    • Java API

    Description

      Problem Statement

      In JIRA 7.3 API, method getCustomFieldObjectsByName() doesn't accept the right input parameter.

      Expected behavior

      The method is supposed to accept input parameter and return output value in the following manner:

      - For input parameter
      • If there's a translation for the custom field name in the user's profile language, the translated name will be the input parameter
      • If there's no translation for the custom field name in the user's profile language, the untranslated name will be the input parameter
      - For output value
      • If there's a translation for the custom field name in the user's profile language, the translated name will be the output value
      • If there's no translation for the custom field name in the user's profile language, the untranslated name will be the output value

      Actual behavior

      The output value is currently working as expected:

      • The returned value will be the translated name of the field if available in the user's profile language - if not, the untranslated name will be returned

      The input parameter is however working in an unexpected manner:

      • If a custom field is not yet renamed or renamed by a user whereby there's no translation for it in the user's profile language, then the untranslated name of the field is accepted by getCustomFieldObjectsByName()
      • If a custom field is renamed by a user whereby there's a translation for it in the user's profile language, then the translated name of the field in that language is accepted by getCustomFieldObjectsByName()

      Example:

      If there's a translation for a field in Spanish and Japanese, but not in French, then no matter whether the field has been renamed and who did that:

      • If a user with Spanish language runs the method, the translated name in Spanish should be the input parameter
      • If a user with Japanese language runs the method, the translated name in Japanese should be the input parameter
      • If a user with French language runs the method, the untranslated name should be the input parameter

      However, currently, if a Japanese user renames the field, then the input parameter will always be the translated name in Japanese, which is unknown to users with other languages.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Votes:
              42 Vote for this issue
              Watchers:
              32 Start watching this issue

              Dates

                Created:
                Updated: