🐛 Bug Report: Creating a category with a different slug and title will prevent the announcement from being created

[rumiha]

📜 Description

Creating a category with a different slug and title will prevent an announcement from being created with that category selected. Attempting to create a new announcement with such a category will throw the following error:
backstage error Filtered internal error with logId=a4056554bf2c3b3194dc from response insert into "categories" ("slug", "title") values ($1, $2) - duplicate key value violates unique constraint "categories_pkey"

The problem is in CreateAnnouncementPage.tsx, inside the onSubmit method. Function slugs.indexOf(category) will return -1 if the category slug and title are not the same, because it tries to find the category title inside an array of category slugs.

For example, when creating a new announcement, if the user selects the category Test Category and presses the submit button, it will throw an error. This happens because Test Category will not be found with slugs.indexOf(category) since the slug is test-category.

👍 Expected behavior

The code should use the slug from the selected category (not the title) to successfully search the slug array.

👎 Actual Behavior with Screenshots

1. Created new category
   

2. Category created, but slug is different from title
   

3. Creating new announcement and selecting created category
   

4. Clicking submit button and getting error
   

👟 Reproduction steps

1. Created new category
2. Category created, but slug is different from title
3. Creating new announcement and selecting created category
4. Clicking submit button and getting error

📃 Provide the context for the Bug.

No response

🖥️ Your Environment

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

None

[lavanya-sainik-ericsson]

Hey All,

We would like to provide a fix for this bug and contribute in this plugin. Will share the PR soon for review.

[kurtaking]

@lavanya-sainik-ericsson @rumiha -

@lavanya-sainik-ericsson's fix for this is in the latest release.