Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: 6.0.0, 6.1.0
-
Component/s: None
-
Labels:None
-
Support reference count:1
-
Symptom Severity:Severity 3 - Minor
-
Bug Fix Policy:
Description
Issue Summary
In Bitbucket 6.x, while creating a fork we can chose a specific project where the fork should be created. However, the choice is ignored and the fork is created as users' private repository. It is possible to move the repository to a project afterward.
The issue doesn't occur in Stash 3.x - Bitbucket 5.x
Environment
Every environment with Bitbucket 6.x.
Steps to Reproduce
- Create a new project.
- Create a new repository and populate it with files.
- Go to forks -> Create fork
- Select the current or any other project in Fork creation screen
- Click 'Fork repository'
Expected Results
A fork is created in the project selected.
Actual Results
A fork is created as users' private repository in users' space.
(Optional - If Necessary)
Workaround
- Fork a repository
- Move a repository to desired project afterward
Attachments
Issue Links
- causes
-
BSERV-11829 Choosing a project while forking a repository cause Java error in Bitbucket 6.1.0 when personal repositories feature is disabled
-
- Closed
-
- duplicates
-
BBSDEV-19471 Loading...
- mentioned in
-
Page Loading...