Should I be able to change an issue so it becomes part of a different sub-project?
Added by Warren Postma almost 8 years ago
I am seeing a problem where we have Projects, and some sub-projects, and I would like to move some tracker-item (of type task) from a top level project, into a subproject. So far the pattern I observe is that:
- Issues with no child issues migrate fine.
- Issues that have already a parent issue, or already some child issues, do not migrate fine.
- Sometimes a somewhat bogus error is displayed, but mostly, no issue is displayed.
Here is the pattern:
1. I click Edit on the issue.
2. I change the Project from ROOT to SUBPROJECT.
3. I click Submit. No error, and no change. If I go load the issue from another browser tab, the silent failure is revealed to me, but if not, I might not be aware that the submit failed.
4. I make another change. Now I click submit again, and now I get "The issue has been updated by another issue while you were editing it".
5. I reload the original issue, ie https://bugs.mycompany.com/issues/12345, and see that the project has not been changed.
This occurs only for some issues with subtasks, but not ALL issues with subtasks. So I am trying to figure out what is about the subtasks that would prevent it from being moved.
Has anyone else seen this? It could be that the subtasks are on some tracker type which is not enabled in the subproject?
Warren