Modify ↓
#10209 closed enhancement (duplicate)
Allow to deprecate components
| Reported by: | Dirk Stöcker | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.13dev |
| Severity: | normal | Keywords: | component |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
For JOSM we manage the core and also plugins in the same trac instance. Sometimes plugins are integrated into core and thus the components for these are no longer relevant. But there is no possibility to deprecate components.
Deleting the components totally results in problems with searching.
What I would like to see is a method to mark a component as deprecated:
- It is no longer contained in the choice boxes of tickets
- When the component is already assigned, it remains until changed.
Attachments (0)
Change History (4)
comment:1 by , 14 years ago
| Milestone: | → next-major-0.1X |
|---|
comment:2 by , 14 years ago
| Component: | general → ticket system |
|---|---|
| Keywords: | component added |
| Version: | → 0.13dev |
comment:3 by , 10 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Issue is also captured in #11637, so closing this as a duplicate.
comment:4 by , 10 years ago
| Milestone: | next-major-releases |
|---|
Note:
See TracTickets
for help on using tickets.
Yep, this sounds useful and would require a state field for components.