Some of our clients are facing with problem that cannot find Active Sprint while creating new Scheduler Issue. This situation happen when Sprint field is added to the create issue in project A which is set as “classic”“company-managed”, but Sprints are not available in “classic” “company-managed” projects. Additionally software project B might used mixed board - using more than one project A, B, C, then although user can add issue from this project A to Sprint, it’s not designed to work this way.
...
Choose Projects and select a project, or choose View all projects to visit the projects directory.
Select Create project.
Click Change Template, choose Software from top left drop-down list and choose Scrum in Classic Company-managed project or Try a nextTeam-gen managed project.
Double Check that the project you’re creating is the right template. If not, click Change template, and select from the templates you have access to. You can switch between classic Company-managed and nextTeam-gen managed project templates using the link at the bottom of the screen.
Enter a name for your new project, and hit Create.
...
Select the issues you want to migrate and hit Next.
Select Move Issues and hit Next.
On the Select Projects and Issue Types screen, select where the issues from your old project will go. Select a destination project and issue type, and hit Next. This is the issue type that each issue in your old project will become in the new project.
On the Map Status for Target Project screen, select a destination status for each status in your old project. This is the status that each issue in your nextTeam-gen managed project will take on in the new project.
On the final screen, click Confirm.
...