Is it possible to show two levels of issues in a CMS grid-report.
Currently I have made two reports which present a level1->level2 structure, and one level2->level3 structure.
Is is possible to make a report showing level1->level2->level3.
I am using subissues to build the structure.
最佳答案
S
SystemWeaver Support
说
超过6年 以前
Hello Peter,
There is currently no support
for multi-level tree structure views for issues.
There is, however, support for
two-level structuring, primarily to support arbitrarily categorization of
issues.
The reasons for this are the
following:
In SystemWeaver, items are used
for describing various kinds of structures, while Issues are assumed to be
simple elements that are tied to items.
So, tree views of issues is
essentially not regarded as an essential feature.
This is different from other
systems, where issues are the only means of organizing development information,
where tree structures may be essential. (Although the arguments given below
still apply.)
Viewing of tree structures often
requires special support for browsing, avoidance of tree loops and so on. Adding these capabilities to
tree structures of issues would add complexity (of use and within
SystemWeaver).
Efficient viewing of structures
(of any kind) requires a separate pane for the tree structure and a separate
for viewing the content (properties) of the leaves.
This requires valuable space
that should be reserved for the content, which is not really available in the
CMS views.
Thanks,
Systemite Support
1 Comment
SystemWeaver Support
说
超过6年 以前
回答
Hello Peter,
There is currently no support
for multi-level tree structure views for issues.
There is, however, support for
two-level structuring, primarily to support arbitrarily categorization of
issues.
The reasons for this are the
following:
In SystemWeaver, items are used
for describing various kinds of structures, while Issues are assumed to be
simple elements that are tied to items.
So, tree views of issues is
essentially not regarded as an essential feature.
This is different from other
systems, where issues are the only means of organizing development information,
where tree structures may be essential. (Although the arguments given below
still apply.)
Viewing of tree structures often
requires special support for browsing, avoidance of tree loops and so on. Adding these capabilities to
tree structures of issues would add complexity (of use and within
SystemWeaver).
Efficient viewing of structures
(of any kind) requires a separate pane for the tree structure and a separate
for viewing the content (properties) of the leaves.
This requires valuable space
that should be reserved for the content, which is not really available in the
CMS views.
Peter Lydh
Is it possible to show two levels of issues in a CMS grid-report.
Currently I have made two reports which present a level1->level2 structure, and one level2->level3 structure.
Is is possible to make a report showing level1->level2->level3.
I am using subissues to build the structure.
Hello Peter,
There is currently no support for multi-level tree structure views for issues.
There is, however, support for two-level structuring, primarily to support arbitrarily categorization of issues.
The reasons for this are the following:
In SystemWeaver, items are used for describing various kinds of structures, while Issues are assumed to be simple elements that are tied to items.
So, tree views of issues is essentially not regarded as an essential feature.
This is different from other systems, where issues are the only means of organizing development information, where tree structures may be essential. (Although the arguments given below still apply.)
Viewing of tree structures often requires special support for browsing, avoidance of tree loops and so on. Adding these capabilities to tree structures of issues would add complexity (of use and within SystemWeaver).
Efficient viewing of structures (of any kind) requires a separate pane for the tree structure and a separate for viewing the content (properties) of the leaves.
This requires valuable space that should be reserved for the content, which is not really available in the CMS views.
Thanks,
Systemite Support
SystemWeaver Support
Hello Peter,
There is currently no support for multi-level tree structure views for issues.
There is, however, support for two-level structuring, primarily to support arbitrarily categorization of issues.
The reasons for this are the following:
In SystemWeaver, items are used for describing various kinds of structures, while Issues are assumed to be simple elements that are tied to items.
So, tree views of issues is essentially not regarded as an essential feature.
This is different from other systems, where issues are the only means of organizing development information, where tree structures may be essential. (Although the arguments given below still apply.)
Viewing of tree structures often requires special support for browsing, avoidance of tree loops and so on. Adding these capabilities to tree structures of issues would add complexity (of use and within SystemWeaver).
Efficient viewing of structures (of any kind) requires a separate pane for the tree structure and a separate for viewing the content (properties) of the leaves.
This requires valuable space that should be reserved for the content, which is not really available in the CMS views.
Thanks,
Systemite Support
-
Comparing two versions of a structure
-
Context and path language
-
Overview of meta model
-
Importing old data
-
Cannot find multiple version items
-
Accumulated bar chart
-
Cannot remove part - is referenced
-
View of non accessable data
-
Path: How to check if an attribute is empty?
-
List and path language
查看所有33话题