Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6396

JIRA Service Desk 4.2 Organization and Request Participant Field Showing Script Instead Of Text

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 4.3.1
    • 4.2.0, 4.3.0, 4.2.1, 4.2.3
    • Issue View

      Status

      Issue Summary

      JIRA Service Desk 8.2 people module is showing below code for request participant and organization.

      • sd.request.participants.field.name
      • sd.customer.organisations.field.name

      Environment

      JIRA 8.2 (Service Desk 4.2)

      Steps to Reproduce

      1. Install JIRA 8.2 with JIRA Service Desk 4.2
      2. Create a new service desk project and open a ticket

      Expected Results

      It should show organization and participants under people module

      Actual Results

      Notes

      This behavior also affects JQL search, as they need to be indicated in JQL with the key instead of their usual human-readable name:

      Workaround

      -

        1. example.PNG
          example.PNG
          195 kB
        2. screenshot-1.png
          screenshot-1.png
          27 kB
        3. screenshot-2.png
          screenshot-2.png
          79 kB
        4. Screenshot 2019-07-24 at 09.52.09.png
          Screenshot 2019-07-24 at 09.52.09.png
          199 kB
        5. Screenshot 2019-07-24 at 09.52.22.png
          Screenshot 2019-07-24 at 09.52.22.png
          406 kB
        6. Screenshot 2019-07-24 at 09.53.31.png
          Screenshot 2019-07-24 at 09.53.31.png
          101 kB
        7. Screenshot 2019-07-24 at 09.54.06.png
          Screenshot 2019-07-24 at 09.54.06.png
          126 kB
        8. Screenshot 2019-07-24 at 09.55.52.png
          Screenshot 2019-07-24 at 09.55.52.png
          243 kB
        9. Screenshot 2019-07-24 at 09.58.46.png
          Screenshot 2019-07-24 at 09.58.46.png
          214 kB

          Form Name

            [JSDSERVER-6396] JIRA Service Desk 4.2 Organization and Request Participant Field Showing Script Instead Of Text

            After reviewing further, I also see several entries like this which indicate an error.  

             

            2019-08-05 11:58:08,516 JIRA-Bootstrap ERROR      [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Error occurred when fixing customfield id: 10002 : java.sql.SQLRecoverableException: Closed Connection.
            com.querydsl.core.QueryException: java.sql.SQLRecoverableException: Closed Connection
                    at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(DefaultSQLExceptionTranslator.java:39)
                    at com.querydsl.sql.Configuration.translate(Configuration.java:447)
                    at com.querydsl.sql.dml.AbstractSQLClause.close(AbstractSQLClause.java:211)
                    at com.querydsl.sql.dml.SQLUpdateClause.execute(SQLUpdateClause.java:220)
                    at com.atlassian.jira.upgrade.UntranslatedKeyFixer.lambda$tryFixCustomFields$2(UntranslatedKeyFixer.java:210)
                    at com.atlassian.jira.database.DefaultQueryDslAccessor$1.lambda$execute$1(DefaultQueryDslAccessor.java:91)
                    at com.atlassian.jira.database.DatabaseAccessorImpl.executeQuery(DatabaseAccessorImpl.java:74)
                    at com.atlassian.jira.database.DefaultQueryDslAccessor$1.execute(DefaultQueryDslAccessor.java:90)
                    at com.atlassian.jira.upgrade.UntranslatedKeyFixer.tryFixCustomFields(UntranslatedKeyFixer.java:205)
                    at com.atlassian.jira.upgrade.UntranslatedKeyFixer.runOnce(UntranslatedKeyFixer.java:147)
                    at com.atlassian.jira.upgrade.ConsistencyCheckerImpl.checkUntranslatedKeyFixer(ConsistencyCheckerImpl.java:279)
                    at com.atlassian.jira.upgrade.ConsistencyCheckerImpl.initialise(ConsistencyCheckerImpl.java:183)
                    at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:166)
                    at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:146)
                    at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:301)
                    at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:196)
                    at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:137)
                    at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:104)
                    at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
                    at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
                    at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
                    at java.lang.Thread.run(Thread.java:748)
            Caused by: java.sql.SQLRecoverableException: Closed Connection
                    at oracle.jdbc.driver.PhysicalConnection.needLine(PhysicalConnection.java:3247)
                    at oracle.jdbc.driver.OracleStatement.closeOrCache(OracleStatement.java:1392)
                    at oracle.jdbc.driver.OracleStatement.close(OracleStatement.java:1375)
                    at oracle.jdbc.driver.OracleStatementWrapper.close(OracleStatementWrapper.java:119)
                    at oracle.jdbc.driver.OraclePreparedStatementWrapper.close(OraclePreparedStatementWrapper.java:96)
                    at org.apache.commons.dbcp2.DelegatingStatement.close(DelegatingStatement.java:156)
                    at com.querydsl.sql.dml.AbstractSQLClause.close(AbstractSQLClause.java:209)
                    ... 19 more
            

            Matt Thompson added a comment - After reviewing further, I also see several entries like this which indicate an error.     2019-08-05 11:58:08,516 JIRA-Bootstrap ERROR [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Error occurred when fixing customfield id: 10002 : java.sql.SQLRecoverableException: Closed Connection. com.querydsl.core.QueryException: java.sql.SQLRecoverableException: Closed Connection at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(DefaultSQLExceptionTranslator.java:39) at com.querydsl.sql.Configuration.translate(Configuration.java:447) at com.querydsl.sql.dml.AbstractSQLClause.close(AbstractSQLClause.java:211) at com.querydsl.sql.dml.SQLUpdateClause.execute(SQLUpdateClause.java:220) at com.atlassian.jira.upgrade.UntranslatedKeyFixer.lambda$tryFixCustomFields$2(UntranslatedKeyFixer.java:210) at com.atlassian.jira.database.DefaultQueryDslAccessor$1.lambda$execute$1(DefaultQueryDslAccessor.java:91) at com.atlassian.jira.database.DatabaseAccessorImpl.executeQuery(DatabaseAccessorImpl.java:74) at com.atlassian.jira.database.DefaultQueryDslAccessor$1.execute(DefaultQueryDslAccessor.java:90) at com.atlassian.jira.upgrade.UntranslatedKeyFixer.tryFixCustomFields(UntranslatedKeyFixer.java:205) at com.atlassian.jira.upgrade.UntranslatedKeyFixer.runOnce(UntranslatedKeyFixer.java:147) at com.atlassian.jira.upgrade.ConsistencyCheckerImpl.checkUntranslatedKeyFixer(ConsistencyCheckerImpl.java:279) at com.atlassian.jira.upgrade.ConsistencyCheckerImpl.initialise(ConsistencyCheckerImpl.java:183) at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:166) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:146) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:301) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:196) at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:137) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:104) at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31) at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102) at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154) at java.lang.Thread.run(Thread.java:748) Caused by: java.sql.SQLRecoverableException: Closed Connection at oracle.jdbc.driver.PhysicalConnection.needLine(PhysicalConnection.java:3247) at oracle.jdbc.driver.OracleStatement.closeOrCache(OracleStatement.java:1392) at oracle.jdbc.driver.OracleStatement.close(OracleStatement.java:1375) at oracle.jdbc.driver.OracleStatementWrapper.close(OracleStatementWrapper.java:119) at oracle.jdbc.driver.OraclePreparedStatementWrapper.close(OraclePreparedStatementWrapper.java:96) at org.apache.commons.dbcp2.DelegatingStatement.close(DelegatingStatement.java:156) at com.querydsl.sql.dml.AbstractSQLClause.close(AbstractSQLClause.java:209) ... 19 more

            I see the following KEY-FIXER entries in the logs.  

            2019-08-05 09:29:45,106 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Setting application property: com.atlassian.jira.upgrade.untranslatedkeyfixer.disabled to true
            2019-08-05 09:29:45,501 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Application property: com.atlassian.jira.upgrade.untranslatedkeyfixer.disabled=true
            2019-08-05 09:29:45,518 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Running untranslated key fixer...
            2019-08-05 09:29:45,518 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Triggering customfield fixer.
            2019-08-05 09:29:45,745 JIRA-Bootstrap WARN      [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Fixing customfield [name, description] id: 10002 from [sd.customer.organisations.field.name, sd.customer.organisations.desc] to [Organizations, Stores the organizations that are associated with a Service Desk customer portal requests. This custom field is created programmatically and required by Service Desk.]...
            

            Matt Thompson added a comment - I see the following KEY-FIXER entries in the logs.   2019-08-05 09:29:45,106 JIRA-Bootstrap INFO [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Setting application property: com.atlassian.jira.upgrade.untranslatedkeyfixer.disabled to true 2019-08-05 09:29:45,501 JIRA-Bootstrap INFO [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Application property: com.atlassian.jira.upgrade.untranslatedkeyfixer.disabled=true 2019-08-05 09:29:45,518 JIRA-Bootstrap INFO [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Running untranslated key fixer... 2019-08-05 09:29:45,518 JIRA-Bootstrap INFO [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Triggering customfield fixer. 2019-08-05 09:29:45,745 JIRA-Bootstrap WARN [c.a.jira.upgrade.UntranslatedKeyFixer] [KEY-FIXER] Fixing customfield [name, description] id: 10002 from [sd.customer.organisations.field.name, sd.customer.organisations.desc] to [Organizations, Stores the organizations that are associated with a Service Desk customer portal requests. This custom field is created programmatically and required by Service Desk.]...

            @Maciej Swinarski, I actually only have a demo license (working on a purchase) so not sure I can open a case.  I'll try and review the logs to see what I can find. 

            Matt Thompson added a comment - @Maciej Swinarski, I actually only have a demo license (working on a purchase) so not sure I can open a case.  I'll try and review the logs to see what I can find. 

            Hi matt.thompson2, could you please open a support case so we can investigate it. I would like to see your logs, a specially the result of the upgrade task: any log containing "KEY-FIXER" should describe what untranslated keys were found and how they were retranslated. Please have a look at this document to see what should be translated by the upgrade task and what can only be re-translated (like active objects tables) with a special endpoint we have provided: https://confluence.atlassian.com/jirakb/custom-field-names-shows-message-keys-instead-of-values-jraserver-69388-975028931.html

            Maciej Swinarski (Inactive) added a comment - - edited Hi matt.thompson2 , could you please open a support case so we can investigate it. I would like to see your logs, a specially the result of the upgrade task: any log containing "KEY-FIXER" should describe what untranslated keys were found and how they were retranslated. Please have a look at this document to see what should be translated by the upgrade task and what can only be re-translated (like active objects tables) with a special endpoint we have provided: https://confluence.atlassian.com/jirakb/custom-field-names-shows-message-keys-instead-of-values-jraserver-69388-975028931.html

            I just updated to 4.3.1 and that did Not fox it for me. 

            Matt Thompson added a comment - I just updated to 4.3.1 and that did Not fox it for me. 

            Chris Gay added a comment -

            This has been fixed for me by updating Jira Service Desk to 4.3.1

            Chris Gay added a comment - This has been fixed for me by updating Jira Service Desk to 4.3.1

             

            This bug was preventing a marketplace app from working, so I used these commands to update my database (postgresql) directly: 

            UPDATE customfield SET cfname = 'Request participants' WHERE description = 'sd.request.participants.desc';
            UPDATE customfield SET cfname = 'Customer Request Type' WHERE description = 'sd.origin.customfield.desc';
            UPDATE customfield SET cfname = 'Organizations' WHERE description = 'sd.customer.organisations.desc';

             

            Angus Warren added a comment -   This bug was preventing a marketplace app from working, so I used these commands to update my database (postgresql) directly:  UPDATE customfield SET cfname = 'Request participants' WHERE description = 'sd.request.participants.desc' ; UPDATE customfield SET cfname = 'Customer Request Type' WHERE description = 'sd.origin.customfield.desc' ; UPDATE customfield SET cfname = 'Organizations' WHERE description = 'sd.customer.organisations.desc' ;  

            I too am experiencing what @Chris Gay is seeing.  I have a fresh installation on Linux.  Please see the following screenshot for an example:

            This screenshot is from the two affected fields when looking at a customer ticket. 

            Matt Thompson added a comment - I too am experiencing what @Chris Gay is seeing.  I have a fresh installation on Linux.  Please see the following screenshot for an example: This screenshot is from the two affected fields when looking at a customer ticket. 

            Michael, IMHO that is another bug and just slightly related.

            Martin Boehme added a comment - Michael, IMHO that is another bug and just slightly related.

            No problem...

            the bug exists since 2015 (https://jira.atlassian.com/browse/JSDSERVER-2326) and Atlassian ist "GATHERING IMPACT" 

            Michael Kornatzki added a comment - No problem... the bug exists since 2015 ( https://jira.atlassian.com/browse/JSDSERVER-2326 ) and Atlassian ist "GATHERING IMPACT" 

              mswinarski Maciej Swinarski (Inactive)
              dkoh Danson (Inactive)
              Affected customers:
              79 This affects my team
              Watchers:
              80 Start watching this issue

                Created:
                Updated:
                Resolved: