-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2
-
Severity 3 - Minor
-
0
-
Issue Summary
When a Kanban board is grouped by queries that are based on components (e.g. ("component = ABC"), it's not possible to use the "create issue" option directly within the swimlanes when the component name is duplicated across different projects.
Steps to Reproduce
- Create some components in a project
- Create components with the same names in another project
- Setup Kanban board swimlanes: Select Method --> Queries
- Set queries like "component = <project key>"
- On the Kanban board make sure "Group by" is set to "Queries"
- Try to create an issue using "+ Create issue" in any of the swimlanes
Expected Results
As the swimlanes are grouped by components, Jira tries to set the corresponding component when you create an issue directly in the swimlane. It should only consider components available for the projects that are part of the board and create the issue successfully.
Actual Results
Jira is looking for the component name and uses the first (or random?) match that it finds globally (across all components in all projects) and throws an error: "Something's gone wrong".
Browser Dev Tools: "Component id 'xxxxx' is not valid"
The ID in this case would correspond to the component that matches the name, but belongs to a different project.
Workaround
Create issues using the main "Create" button and select the component from the dropdown, as this will only provide components from the selected project.
Other workaround is to change the query to use the component id instead of the name so it selects the correct one upon issue creation
- relates to
-
JSWCLOUD-17042 Make creating a new issue on a company managed Kanban board more obvious
- Gathering Interest