| Reporter |
Anton Kravtsov (AntonK)
|
|---|---|
| Created | Mar 21, 2012 8:40:37 PM |
| Updated | Apr 10, 2013 1:02:52 PM |
| Priority | Normal |
| Type | Feature |
| State | Open |
| Assignee | Evgeniy Schepotiev (zeckson) |
| Subsystem | No subsystem |
| Fix versions | Backlog |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Undefined |
The system already supports the dependency "Depends on / Is required for".
After the subtasks support is implemented (like JT-571), I expect we'll get the dependency "Contains / Is part of".
After that all issues within a project may be organized in a hierarchy (under a top-most item) with dependencies between nodes (issues), which allows to see the project's tasks as a Gantt chart. (it may be generated either by YouTrack or by a stand-alone tool).
As soon as all tasks' durations (efforts) are estimated (in hours/days/etc.), the data in YouTrack can nicely represent the project's structure (and I can get rid of MSProject-like tools :).
As an alternative: exporting issues in the format for subsequent import into MSProject
So the buzzword is Gantt chart.
After the subtasks support is implemented (like JT-571), I expect we'll get the dependency "Contains / Is part of".
After that all issues within a project may be organized in a hierarchy (under a top-most item) with dependencies between nodes (issues), which allows to see the project's tasks as a Gantt chart. (it may be generated either by YouTrack or by a stand-alone tool).
As soon as all tasks' durations (efforts) are estimated (in hours/days/etc.), the data in YouTrack can nicely represent the project's structure (and I can get rid of MSProject-like tools :).
As an alternative: exporting issues in the format for subsequent import into MSProject
So the buzzword is Gantt chart.