Fix duplicate key jsds.requestTypeField.priority.label error in Jira Service Management Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This article helps you fix duplicate key error similar to jsds.requestTypeField.<ID>.priority.label during integrity checks in Jira Service Management Data Center.
Environment
Jira Service Management Data Center
Diagnosis
If you notice the error similar to Duplicate key jsds.requestTypeField.<ID>.priority.label during integrity checks in Jira Service Management Data Center, you are encountering a configuration problem where at least one request type has a duplicated Priority field definition, resulting in inconsistent request type configuration data.
Cause
This error occurs when a Jira Service Management request type contains duplicate field configurations. The exact cause of the duplication is not yet known, but it results in an error similar to the one below. In this example, the Priority field is duplicated.
Duplicate key jsds.requestTypeField.1234.priority.label (attempted merging values Priority and Priority)
java.lang.IllegalStateException: Duplicate key jsds.requestTypeField.1234.priority.label (attempted merging values Priority and Priority)
at java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:135)
...
at com.atlassian.servicedesk.plugins.lingo.integration.internal.provider.RequestTypeTranslationKeysGroupProvider.getRequestTypeFieldsKeys(RequestTypeTranslationKeysGroupProvider.java:73)
at com.atlassian.servicedesk.plugins.lingo.integration.internal.provider.RequestTypeTranslationKeysGroupProvider.getRequestTypeTranslationKeys(RequestTypeTranslationKeysGroupProvider.java:55)
at com.atlassian.servicedesk.plugins.lingo.integration.internal.provider.RequestTypeTranslationKeysGroupProvider.lambda$getKeys$1(RequestTypeTranslationKeysGroupProvider.java:48)
...
at com.atlassian.servicedesk.plugins.lingo.integration.internal.manager.ProjectLanguageSettingsInternalManager.getProjectSettings(ProjectLanguageSettingsInternalManager.java:114)
...
at com.atlassian.servicedesk.plugins.lingo.integration.internal.provider.RequestTypeTranslationKeysGroupProvider.getKeys(RequestTypeTranslationKeysGroupProvider.java:49)
at com.botronsoft.jira.jiraservicedeskintegration.ServiceDeskServiceFacade.getServiceDesk(ServiceDeskServiceFacade.java:97)
at com.botronsoft.jira.rollout.impl.convert.servicedesk.ServiceDeskTransformer.transform(ServiceDeskTransformer.java:103)
at com.botronsoft.jira.rollout.jobs.IntegrityCheckProgressInterceptor.invoke(IntegrityCheckProgressInterceptor.java:117)
at com.botronsoft.jira.rollout.impl.integrity.DuplicateObjectInterceptor.invoke(DuplicateObjectInterceptor.java:53)
at com.botronsoft.jira.rollout.impl.integrity.ConversionInterceptor.invoke(ConversionInterceptor.java:77)
at com.botronsoft.jira.rollout.impl.configuration.AbstractConfigurationExportStrategy.exportServiceDesks(AbstractConfigurationExportStrategy.java:327)
...
at com.botronsoft.jira.rollout.jobs.IntegrityCheckJob.call(IntegrityCheckJob.java:21)
Solution
Use the steps below to identify the affected request type and remove the duplicate field configuration.
1. Identify the affected request type ID from the error
Notice this error fragment:
Duplicate key jsds.requestTypeField.1234.priority.label (attempted merging values Priority and Priority)Note the numeric value between
jsds.requestTypeField.and.priority.label. This value is the request type ID. For example, in the message above, the request type ID is1234.
2. Use SQL to find the affected project and request type
Run the following SQL query against your Jira database to identify which Jira Service Management project and request type are associated with the request type ID you found.
Replace <Request_Type_ID> with the ID from the error message. In our example, it would be 1234.
SELECT vp."NAME" as Project,
upper(vp."KEY") as Project_key,
form."NAME" as Request_Type,
form."ID" as Request_Type_ID
FROM "AO_54307E_VIEWPORTFORM" form
JOIN "AO_54307E_VIEWPORT" vp ON vp."ID" = form."VIEWPORT_ID"
WHERE form."ID" = <Request_Type_ID>;For databases other than PostgreSQL, you may need to remove the double quote (") characters from the query before running it.
Confirm that the query returns a single row with:
Project: the Jira Service Management project name.
Project_key: the project key.
Request_Type: the affected request type name.
Request_Type_ID: the ID you used in the query.
3. List the fields configured for the affected request type
Now query the request type fields to check for duplicates and double-check that the problem is present.
Run this SQL query, replacing <Request_Type_ID> with the same value used before:
SELECT field."FIELD_ID",
field."FIELD_TYPE",
field."LABEL",
field."REQUIRED"
FROM "AO_54307E_VIEWPORTFIELD" field
WHERE field."FORM_ID" = <Request_Type_ID>; Run the query against the Jira database.
Review the results and look for duplicate fields.
Save the query results before making any changes, in case you need to refer back to them.
4. Fix the duplicate field configuration in the user interface
Once you have identified the affected project and request type, adjust the configuration in the Jira Service Management project settings.
In Jira, go to the affected Jira Service Management project.
Open the project settings.
Go to the request type configuration screen.
Select the request type identified in the first SQL results (the Request_Type value).
Remove the affected field.
Save the configuration.
Refresh the request type configuration page in your browser.
Confirm that the field is no longer present on the form.
Add the field back to the form if you still want it available for this request type.
Save the configuration again.
After you complete these steps, re-run the operation that previously failed and confirm that the duplicate key error no longer appears.
5. If the error persists
If the duplicate key error persists after updating the request type fields through the UI, you may need to perform a direct database cleanup on the AO_54307E_VIEWPORTFIELD table.
Do not run DELETE or UPDATE statements directly on the Jira database unless you are fully confident in what you’re doing and have a recent, thoroughly tested backup available.
If you’d like guidance on how to proceed, create or update an Atlassian support request and attach:
The full error message, including the duplicate key details.
The results of both SQL queries for the affected request type.
Was this helpful?