-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
7.0.0, 7.2.0, 7.1.2, 7.1.9, 7.3.3, 7.6.3
-
7
-
9
-
Severity 2 - Major
-
4
-
Summary
JIRA contains the ability to pre-populate certain fields of new issues created directly from an agile board so that they remain on the board. However if the board is set up to filter only on a project and component and the same component name exists for another project the component will not be populated.
Steps to Reproduce
- Create a JIRA Software project, “scrum1", and add the component ‘test’ to the project
- Create a few issues with this component
- Create a board based on the filter “project = scrum1 and component = test”
- View the backlog and create a new issue by clicking on the + Create Issue option from the bottom of the backlog
(the new issue should be created with the component - test) - Create a second JIRA Software project and add the component ‘test’ to it
- Return back to the original board and create an issue. The issue will be created without a component, and therefore will not appear on the board
Expected Results
The issue should be created on the board as there is only one component being filtered.
Actual Results
The issue is created without a component and does not appear on the board
Workaround
- Rename one of the components so that the component names are all unique.
- It would also be possible to create an Automation Rule (A4J) that would run on the specific project that would add the desired Component. (Pre-populate the Component/s field while creating an issue from the Board View)
- This is a simple example rule that would add the Component 'TEST' for all the issues created on that project from both the 'Jira Create Screen' and the 'Backlog View'. Some adjustments might be necessary to meet your specific requirements.
- When creating an issue from the backlog view, the message "The issue KEY-X has been created but is not currently visible" will still be displayed right after it is created; however, the issue will be shown in the Backlog after refreshing the page.
- is related to
-
-
- Closed
-
-
-
- Gathering Impact
-
- mentioned in
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-14728] Multiple components with the same name prevents auto-population of component when created from board
We are in the same situation as April has stated above. The name of product components need to match over different projects and each team has its own agile board. It is a very huge problem and the workaround mentioned above cannot solve the issue, when the components need to have the same name.
Is there a timeline for this bug to be fixed?
Or does anyone have another idea how to deal with it?
Thanks
The Workaround doesn't seem to be working anymore. So: We have a pretty big issue for bigger teams here, with no available workaround.
We are also affected by this issue and would appreciate a fix. Cheers matthias
This is also a huge problem for us, we use the "quick create" feature in our deployment of Jira on a daily basis, when we create the issues to not have them show up on the board is a major pain point.
Workaround for now is fine, but this does affect our support staff and user group dramatically.
This is a huge problem for us, due to:
- We have multiple teams working on the same product(s)
- We use Agile and Portfolio, and the only way to get team-level stats AND product-component stats is to use the same component names in multiple projects, but give each team it's own board
- Service teams enter most bugs and improvements, and asking new joiners to remember multiple names for the same thing and/or teaching them all advanced search is not a realistic solution for this defect
I doubt we are your only Jira Software customers who have Portfolio and need to report on activity, so please prioritize this issue.
Thanks!
This is also a problem we have been having +1 to hopefully getting this fixed