You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I use multi-sprint structure to promote backlog tasks to the status like "it has to be done sooner then other ones". It results in having e.g. 3 sprints and the main backlog. Backlog is for me the place where i put the less important tasks. One sprint (placed directly above the backlog) serves as an idea incubator (I put there bigger functionalities that require some special attention before being split into stories). This sprint has been always inactive. My second sprint is called "Call for implementation" where I put all tasks the need to be included in the next sprint. My third sprint (placed at the top) is the active one.
When I add a new task using + button inside one of inactive secondary sprints ("incubator" or "call for implementation"), this task is put into the main backlog. I have to scroll down to the bottom of the backlog to find it and move it to the sprint from which I have created this task.
Am I doing sth wrong / improper? IMO it should all work smoothly. Can I make some workaround to have my new task landed directly into a specific sprint?
Hello @Maciej Kaniewski
Welcome to the Atlassian community.
Are you working with a Team Managed project or a Company Managed project? That information will show at the bottom of the navigation panel on the left.
Is there an Automation Rule running that is automatically pulling the issue out of the inactive sprint? Check the Automation Panel for the issue. You may need to click the Refresh button in that panel.
Also check the History for the issue to see if the Sprint field is being set and then being cleared.