Added by Martin Heitmann 5 days ago
Hello everyone
I have an issue with the backlogs view. Previously I copied the work package type task as a new kind of work package and slightly enhanced the code so that all these new tasks are assigned to a product backlog right from the start. This works. And I can also manually assign them to other versions/sprints. But when I turn to the backlogs view, I experience a small problem. Usually, I would move work packages from one version backlog to another - at least that's how I do it with JIRA. Here, I can move them around and they appear to stick to the other version backlogs. But, as soon as I turn my back on them or actually I open another site in my openproject instance and go back to the backlog page, they are again in the product backlog from which they came. This is only different, when I move them to another version backlog and then open one of them from there. Then I get the details page for that work package and it shows the new and correct version. And when I return to the backlog page, this particular work package is correctly in its new place in the other version backlog. But all other work packages that I moved around have again returned to their home base.
As I don't want to enter each detail page after moving one work package, I would ask for your advice. I am using version 15.5.1, which is the current one from my linux distribution's repo.
BR
Martin
Replies (3)
Hello Martin,
I cannot evaluate your code adjustments, but these two pieces of information may be helpful:
By default, only work packages that are available in the project are displayed in version boards or backlogs in a project.
You can share versions with all projects and then link work packages from different projects to versions. However, you cannot see all of them in the respective boards in the projects. Instead, you can use the work package table. There you can display the work packages of several projects. I suspect that this mechanism might have something to do with this issue.
This feature request aims to change that:
At the same time, I would like to point out that OpenProject 16.6.1 is available for all officially supported Linux distributions. I suspect that you see that there are no new package resources. This is because you need to update the package sources for a major release. This is described in more detail here -> [1]
Best,
Alexander
[1] https://www.openproject.org/docs/installation-and-operations/operation/upgrading/#major-upgrades
Dear Alexander
Thank you very much. The update to 16.6.1 did the trick. :)
That's great news. Thank you for your follow-up. I close / lock this thread then.
Best
Alexander