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

Adding an archived component on the Issue View Screen throws Communication Breakdown error


      Issue Summary

      Jira does not throw a business error when an archived component is added to an issue whereas the component is detected as a new one. 

      Steps to Reproduce

      1. Create a new label named test and use it in an issue
      2. Archive the component
      3. Create another component or ensure that there is some other components in the project. Otherwise, the component selection is not possible in the next step
      4. Create another issue and browse it
      5. Click on the component to add the Test (first letter as uppercase) component

      Expected Results

      Jira should say that there is already the same component in the archived components

      Actual Results

      The component is detected as a new one:

      The page keeps loading and it needs to be refreshed.

      Also, the below exception is thrown in the xxxxxxx.log file:

      2023-10-26 11:29:03,564+0000 http-nio- ERROR      [o.a.c.c.C.[.[localhost].[/jira].[action]] Servlet.service() for servlet [action] in context with path [/jira] threw exception [java.lang.IllegalArgumentException: Component name = 'Test' is not unique] with root cause java.lang.IllegalArgumentException: Component name = 'Test' is not unique
      	at com.atlassian.jira.bc.project.component.CachingProjectComponentStore.createIllegalArgumentExceptionForName(CachingProjectComponentStore.java:355)
      	at com.atlassian.jira.bc.project.component.CachingProjectComponentStore.insert(CachingProjectComponentStore.java:296)
      	at com.atlassian.jira.bc.project.component.CachingProjectComponentStore.store(CachingProjectComponentStore.java:212)
      	at com.atlassian.jira.bc.project.component.DefaultProjectComponentManager.create(DefaultProjectComponentManager.java:107)
      	at com.atlassian.jira.issue.fields.ComponentsSystemField.updateIssue(ComponentsSystemField.java:542)
      	at com.atlassian.jira.bc.issue.DefaultIssueService.updateIssueFromFieldsWithScreenCheck(DefaultIssueService.java:859)
      	at com.atlassian.jira.bc.issue.DefaultIssueService.updateIssueFromFields(DefaultIssueService.java:841)
      	at com.atlassian.jira.bc.issue.DefaultIssueService.validateAndUpdateIssueFromFields(DefaultIssueService.java:722)


      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Unassigned Unassigned
            ayanar Alp
            3 Vote for this issue
            5 Start watching this issue