View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008559 | mantisbt | administration | public | 2007-11-08 05:25 | 2008-02-04 09:07 |
Reporter | brody | Assigned To | |||
Priority | normal | Severity | trivial | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | 1.0.7 | ||||
Summary | 0008559: project management - interpretation/consequence of project status (and enabled) | ||||
Description | Hi, found no hints in the current documentation (as of V1.0.0). Need to know, what the project states (development, release, stable, obsolete) has to be interpreted and have consequences in project controlling (and seeing from others). Know, that status "not enabled" does show project neither in project selector nor in summary and subprojects of this project gets moved one stage higher. | ||||
Additional Information | Need a combination, that makes impossible setting new issues on the project (which is head of sub projects), but gives the possibility for searching, summarizing of all subprojects .. any idea? Setting "disabled", does not help. | ||||
Tags | project_management | ||||
I have exactly the same question (using 1.1.1). Setting obsolete seems not have any effect whatsoever, while I would expect it to either
The 'enabled' setting does perform like I expect, it completely removes the project and its issues from my radar. |
|