I found a similar question here, https://answers.atlassian.com/questions/238568/how-to-have-cloned-items-not-assigned-to-the-sprint-automatically, but since it wasn't really answered I'll try my own.
We have some "time-tracking" tasks today to have some control of time not spent on development during the sprints. These tasks are usually cloned from sprint to sprint.
Now, it have come to my attention that if you clone an issue, the link to the sprint is included. And if you clone something that was previously cloned, you get quite an active list of sprints.
Continued, if you search for the issue in one of the sprints that is stated as "active sprint", you are unable to find the issue, so in practice there is no way to remove this link. So I have the following situation:
So in practice the issue has been a member of two sprints that was completed before the issue was even created.
I would say that keeping the Jira Agile link when cloning an issue is a bug because this information cannot be removed. But I can live with this being an improvement if I can get access to functionality to change this information.
Does anyone else have comments in this regards?
(And no, buying yet another plugin to Jira is not an option)
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG