User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041223 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041223 Firefox/1.0 My company is getting bigger, to the point where it would be nice if there was N-Level classification support, where the admin defined how many levels. I believe this could be done by adding a "level" column in the classification level and the "id" column would point to either a class_id or product_id (for level 0). The advanced query would have to be updated, but I don't think any of the reports/graphs would have to change. Reproducible: Always Steps to Reproduce:
Hrm, did we not already have this filed somewhere?? I'd think this is a dupe...
BTW, similar to #277080, I'd like to see multiple classificiations with the same name in different classifications.
*** This bug has been marked as a duplicate of 43940 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → DUPLICATE
These bugs are *not* duplicates of each other. The ability to have an infinite level of classifcations is not the same as having *one object type* which represents them all. Perhaps the summaries are not fully clear.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Oh, wait, I just actually *looked* at the bug this was duped to. No, component trees are extremely complex and unnecessary. I much prefer N-Level Classifications.
*** Bug 320227 has been marked as a duplicate of this bug. ***
My company currently has 300+ products and could easily increase several times. As such, having a N-level classification (combined with bug #277080) would be a big win. Classification-wide reports, groups, etc. would also be a big win. This is a more enterprise class of features. I know this is a lot of work, but it's what my company is now looking for.
Whiteboard: [roadmap: 3.2]
I forgot, one can also add a hierarchical menu to indicate which product for cloning a ticket.
That's an interesting solution. I don't think it's exactly what we'd do upstream, but it's something to think about.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.