-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
6.6.2
-
1
-
Severity 3 - Minor
-
0
-
Issue
Bamboo should not allow duplicate Repository Name under Plan configuration >> Repositories tab, even if coming from difference sources (e.g Linked repository and Plan Repository)
How to replicate
- create a Linked repository (e.g Repository Name as My Repo)
- create a Plan (e.g PROJ-PLAN)
- create a plan repository under Plan configuration >> Repositories tab (e.g Repository Name as My Repo)
- add Linked Repository My Repo to the same Plan configuration >> Repositories tab
Notes
If you attempt on modifying any repository configuration on Plan Repository added, an error message gets thrown:
- Display name should be unique within the plan
- is cloned as
-
BDEV-14914 Failed to load
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BAM-20076] Plan configuration should not allow duplicate Repository Name
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
| Labels | Original: bamboo-bugfix-kanban-candidate pse-request | New: bamboo-bugfix-kanban-candidate cleanup-seos-fy25 pse-request |
| UIS | Original: 1 | New: 0 |
| UIS | New: 1 |
| Remote Link | Original: This issue links to "BDEV-14914 (Jira)" [ 390677 ] | New: This issue links to "BDEV-14914 (Hello Jira)" [ 390677 ] |
| Status | Original: Gathering Impact [ 12072 ] | New: Long Term Backlog [ 12073 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 2809288 ] | New: JAC Bug Workflow v3 [ 3384468 ] |
| Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Bamboo Data Center, please check our public roadmap.
Kind regards,
Bamboo Data Center