-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
-
None
-
Severity 3 - Minor
Issue Summary
- Jira Slack integration throwing error when duplicate custom field names exist
- Affecting Jira Server for Slack version 2.0.1.
Steps to Reproduce
- Configure a Slack integration in Jira
- Create duplicate custom field with the name 'Category' (
Other duplicated custom fields are affected too)
- Configure the Notify Slack post-function
Expected Results
Renderer works fine and notifications are sent correctly.
Actual Results
- The notification preview in Notify Slack post-function throws the following error:
Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8)
- The notification in Slack breaks with the error
Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation.
Notes
The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the Duplicate key error.
Workaround
Do not use custom fields with the same name
OR
Revert to the add-on's version 1.1.11 which is not affected from here
[API-156] Having a duplicate custom field name breaks the Notify Slack post-function renderer and the notification
Resolution | New: Fixed [ 1 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Description |
Original:
h3. Issue Summary
* Jira Slack integration throwing error when duplicate custom field names exist * Affecting [Jira Server for Slack|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official?hosting=server&tab=overview] version *2.0.1*. h3. Steps to Reproduce # Configure a Slack integration in Jira # Create duplicate custom field with the name 'Category' ((i) _Other duplicated custom fields are affected too_) # Configure the Notify Slack post-function h3. Expected Results Renderer works fine and notifications are sent correctly. h3. Actual Results * The notification preview in Notify Slack post-function throws the following error: {code:none} Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8) {code} * The notification in Slack breaks with the error {quote}_Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation._ {quote} h3. Notes The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the _Duplicate key_ error. h3. Workaround Do not use custom fields with the same name OR Revert to the add-on's version *1.1.11* which is not affected from [here|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official/version-history] |
New:
h3. Issue Summary
* Jira Slack integration throwing error when duplicate custom field names exist * Affecting [Jira Server for Slack|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official?hosting=server&tab=overview] version *2.0.1*. h3. Steps to Reproduce # Configure a Slack integration in Jira # Create duplicate custom field with the name 'Category' ((i) _Other duplicated custom fields are affected too_) # Configure the Notify Slack post-function h3. Expected Results Renderer works fine and notifications are sent correctly. h3. Actual Results * The notification preview in Notify Slack post-function throws the following error: {code:none} Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8) {code} * The notification in Slack breaks with the error {quote}_Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation._ {quote} h3. Notes The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the _Duplicate key_ error. h3. Workaround Do not use custom fields with the same name OR Revert to the add-on's version *1.1.11* which is not affected from [here|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official/version-history] |
Description |
Original:
h3. Issue Summary
* Jira Slack integration throwing error when duplicate custom field names exist * Affecting [Jira Server for Slack|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official?hosting=server&tab=overview] version *2.0.1*. h3. Steps to Reproduce # Configure a Slack integration in Jira # Create duplicate custom field with the name 'Category' # Configure the Notify Slack post-function h3. Expected Results Renderer works fine and notifications are sent correctly. h3. Actual Results * The notification preview in Notify Slack post-function throws the following error: {code:none} Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8) {code} * The notification in Slack breaks with the error {quote}_Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation._ {quote} h3. Notes (i) Other duplicated custom fields might be affected too. The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the _Duplicate key_ error. h3. Workaround Do not use custom fields with the same name OR Revert to the add-on's version *1.1.11* which is not affected from [here|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official/version-history] |
New:
h3. Issue Summary
* Jira Slack integration throwing error when duplicate custom field names exist * Affecting [Jira Server for Slack|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official?hosting=server&tab=overview] version *2.0.1*. h3. Steps to Reproduce # Configure a Slack integration in Jira # Create duplicate custom field with the name 'Category' ((i) _Other duplicated custom fields are affected too_) # Configure the Notify Slack post-function h3. Expected Results Renderer works fine and notifications are sent correctly. h3. Actual Results * The notification preview in Notify Slack post-function throws the following error: {code:none} Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8) {code} * The notification in Slack breaks with the error {quote}_Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation._ {quote} h3. Notes The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the _Duplicate key_ error. h3. Workaround Do not use custom fields with the same name OR Revert to the add-on's version *1.1.11* which is not affected from [here|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official/version-history] |
Description |
Original:
h3. Issue Summary
* Jira Slack integration throwing error when duplicate custom field names exist h3. Steps to Reproduce # Configure a Slack integration in Jira # Create duplicate custom field with the name 'Category' # Configure the Notify Slack post-function h3. Expected Results Renderer works fine and notifications are sent correctly. h3. Actual Results * The notification preview in Notify Slack post-function throws the following error: {code:none} Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8) {code} * The notification in Slack breaks with the error {quote}_Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation._ {quote} h3. Notes (i) Other duplicated custom fields might be affected too. The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the _Duplicate key_ error. h3. Workaround Do not use custom fields with the same name |
New:
h3. Issue Summary
* Jira Slack integration throwing error when duplicate custom field names exist * Affecting [Jira Server for Slack|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official?hosting=server&tab=overview] version *2.0.1*. h3. Steps to Reproduce # Configure a Slack integration in Jira # Create duplicate custom field with the name 'Category' # Configure the Notify Slack post-function h3. Expected Results Renderer works fine and notifications are sent correctly. h3. Actual Results * The notification preview in Notify Slack post-function throws the following error: {code:none} Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8) {code} * The notification in Slack breaks with the error {quote}_Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation._ {quote} h3. Notes (i) Other duplicated custom fields might be affected too. The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the _Duplicate key_ error. h3. Workaround Do not use custom fields with the same name OR Revert to the add-on's version *1.1.11* which is not affected from [here|https://marketplace.atlassian.com/apps/1220099/jira-server-for-slack-official/version-history] |
Remote Link | New: This issue links to "Duplicate custom field names cause post-function renderer error (Web Link)" [ 447168 ] |
Description |
Original:
h3. Issue Summary
* Jira Slack integration throwing error when duplicate custom field names exist h3. Steps to Reproduce # Configure a Slack integration in Jira # Create duplicate custom field with the name 'Category' # Configure the Notify Slack post-function h3. Expected Results Renderer works fine and notifications are sent correctly. h3. Actual Results * The notification preview in Notify Slack post-function throws the following error: {code:none} Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8) {code} * The notification in Slack breaks with the error {quote}_Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation._ {quote} h3. Notes The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the _Duplicate key_ error. h3. Workaround Do not use custom fields with the same name |
New:
h3. Issue Summary
* Jira Slack integration throwing error when duplicate custom field names exist h3. Steps to Reproduce # Configure a Slack integration in Jira # Create duplicate custom field with the name 'Category' # Configure the Notify Slack post-function h3. Expected Results Renderer works fine and notifications are sent correctly. h3. Actual Results * The notification preview in Notify Slack post-function throws the following error: {code:none} Error rendering preview Duplicate key JiraPostFunctionEventRenderer.CustomFieldWrapper(field=Category, issue=com.atlassian.jira.plugins.slack.web.rest.SlackMessageResource$1@432a38d8) {code} * The notification in Slack breaks with the error {quote}_Error in Notify Slack configuration for project XXX. Please contact your administrator to make sure that Notify Slack post-function comes after the issue creation._ {quote} h3. Notes (i) Other duplicated custom fields might be affected too. The plugin pre-populates values of all custom fields for message rendering, thus it is breaking the rendering with the _Duplicate key_ error. h3. Workaround Do not use custom fields with the same name |