Suggestion: parent-child constraints based on tracker
Currently I am evaluating Redmine 1.0 subtasking.
I am finding this feature very useful.
Although, I think, there should be some constraints - what can be parent task and what child tasks it may include.The reasons for this are the following:
- Each tracker should (IMHO) serve certain needs, e.g. feature represents a request for a new functionality while defect - an issue in the existing. It is, so to say, micro-management level.
- Needs for the parent tasks are different, I would say it is macro-level for project planing and tracking.
- Not every parent-child combination may have sense, for example feature-defect vs defect-feature
- Such restriction would force the users to follow the workflow, accepted in the company
Thus, it would be good if the users (local Redmine admins) would be able to create constrains on the tracker level, specifying what parent-child relationships are allowed, and what trackers may have no parent. Similar to what you have for allowing status transitions.
Did this topic lead anywhere? We're having similar requirements, constraints on parent-child-relationships based on the tracker-type, constraints on types of related issues also based on the tracker-types: So I'd really like to know if you've gotten any responses here or in some other thread...
RE: Suggestion: parent-child constraints based on tracker - Added by Eugene Hutorny about 5 years ago
I am not aware about any outcome of this topic