Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-26244

creating an issue from Advanced Roadmap with grouped components can cause error "Component id is not valid"

XMLWordPrintable

      Issue Summary

      Using the view settings to group by components, using components from different projects will lead to error Component id is not valid, when syncing created issues back to Jira

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Create two projects with several components and have the issues assigned to these different components
      2. Create a plan selecting both projects as the issue sources
      3. Create a view with components from both projects in one group
      4. Within one group take an issue, click on the three dots to create a story (or an epic)
      5. Note that the component(s) is already filled in.
      6. Select Review Changes, and sync this change (Issue created and 2 fields (priority and component)

      Expected Results

      The issue gets created with the component matching the project

      Actual Results

      The change can't be committed to Jira. The error message in the dialog states "Change could not be committed for unknown reason".

      The below exception is thrown in the atlassian-jira.log file:

      2024-12-11 12:53:07,516+0000 http-nio-8080-exec-14 url: /jira/rest/jpo/1.0/issues/commit; user: admin WARN admin xxx /rest/jpo/1.0/issues/commit [c.a.r.j.c.scenario.common.BaseScenarioEntityCommitService] Error in commit operation.
com.atlassian.rm.jpo.env.issues.EnvironmentIssueCreateException: Specific error details: {components=Components Billing(10001) are not valid for project 'SCRUM'.}
	at com.atlassian.rm.jpo.env.issues.JiraIssueService.createIssue(JiraIssueService.java:683)

      The component listed in the error is the component from the other project, that is part of the group. It looks as if Advanced Roadmap is trying to add all components of the group instead of only the ones valid for that specific project.

      Workaround

      Option 1

      Create the issues while in a view, that is not using the grouping

      Option 2

      Before Reviewing the changes and saving them to Jira, add another component to the ticket and remove that component again. This can also be done after the first try to save the changes to Jira failed.
      Now the save will succeed.

            [JSWSERVER-26244] creating an issue from Advanced Roadmap with grouped components can cause error "Component id is not valid"

            There are no comments yet on this issue.

              Unassigned Unassigned
              cpostma@atlassian.com Conny Postma
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated: