-
Type:
Suggestion
-
Resolution: Duplicate
-
Component/s: Repository - Issues
Hi everybody! i noticed that forking a mercurial repo with bitbucket, doesn't inherit in the new fork current issues and tracker settings.
Well, that's probably because unresolved issues aren't linked to any commit and components/milestones too, so it's not possibile to determine what issue/component/milestone inherite and what not.
So maybe an import/export feature it will more easy to achieve and will help people that needs all the old settings in the new fork.
Thank you.