View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
---|---|---|---|---|---|---|---|---|---|
0000540 | v3.2 Release | Tasks | public | 2010-08-08 23:23 | 2014-07-16 21:30 | ||||
Reporter | opto | ||||||||
Assigned To | caseydk | ||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Product Version | |||||||||
Target Version | Fixed in Version | 3.2 | |||||||
Summary | 0000540: Import tasks: incorrect handling of subprojects | ||||||||
Description | At the moment, import tasks copies the subproject token tasks, but this is then orphaned (not related to any subprokject). Solutions: 1) on import, copy the subproject and enter the copy's token task into the imported tasks 2) allow m:1 relationships for subprojects (multiple parents)and insert as additional parent of original subproject maybe user ahould decide whether 1 or 2 (checkbox) Improvement: not project should own subproject, but a task should own a subproject (if m:1 relations are implemented) | ||||||||
Tags | No tags attached. | ||||||||
Attached Files |
|
![]() |
|||||||
|
![]() |
|
caseydk (administrator) 2014-06-13 21:35 |
Resolved with the Project owning the Subproject: https://github.com/web2project/web2project/commit/d30c4b43c34b5308c72f670a4b9775a21dad3ffe While it may create the occasional unexpected result, this is literally the only report in four years, so it should be exceptionally rare. |
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2010-08-08 23:23 | opto | New Issue | |
2010-09-07 14:11 | caseydk | Project | v2.1 Release (Closed) => Pending Requests |
2014-06-13 21:30 | caseydk | Category | General => Tasks |
2014-06-13 21:30 | caseydk | Project | Pending Requests => v3.2 Release |
2014-06-13 21:35 | caseydk | Note Added: 0003475 | |
2014-06-13 21:35 | caseydk | Status | new => resolved |
2014-06-13 21:35 | caseydk | Fixed in Version | => 3.2 |
2014-06-13 21:35 | caseydk | Resolution | open => fixed |
2014-06-13 21:35 | caseydk | Assigned To | => caseydk |
2014-06-17 18:50 | caseydk | Relationship added | related to 0000484 |
2014-07-16 21:30 | caseydk | Status | resolved => closed |