-
State changed as build OD-7720 (16.1.0) is successful
-
OneDev
changed state to 'Closed' 2 weeks ago
Previous Value Current Value Open
Closed
-
This breaks a key feature of having a parent project structure in the first place though. Creating a feature issue that requires changes to multiple child projects now requires touching each child project. Or am I thinking about this wrong?
-
Setting inheritance and project organization still benefits from tree structure. For the scenario you mentioned, I'd suggest to add sub issues in each child project and link to feature issue. Then fix sub issues in each child project.
-
Agreed the tree structure has many benefits just not this one anymore. Tested your suggestion and you’re right, that works. I lose my workflow of commit closes issue and now have commit closes “sub” issue that links to parent issue. I don’t know that I experienced heavy performance hits before. (Shrugs) I assume I am much smaller scale than those experiencing the performance reduction.
anywho thanks for being responsive, I still love the platform.
-
And closing all sub issues will close parent issue automatically.
Peformance will not be a problem for dozens or hundreds of projects. But we have users managing tens of thousands of projects, and that will be an issue when set up cross project links between issues and commits.
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Currently we can define issues in parent projects, and fix it in child project, and OneDev will link commits from child projects with the issues. However this cause serious performance problems when there are many child projects as OneDev needs to scan all child projects to find commits which can be very slow.