Opened 16 years ago
Closed 16 years ago
#7411 closed enhancement (duplicate)
Components [ticket system] should be accessible through the wiki (see attachments)
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.11 |
| Severity: | major | Keywords: | tickets components wiki |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
it is very annoying, that one have to: 1) create components inside the admin-tickets section 2) create SAME components inside the wiki
what if i have dozens of components?
while i am sure, that i'm not the first one to notice this issue, i couldn't find existing tickets about it, sorry. perhaps, if someone find such tickets, he could link my attachments there.
slightly offtopic: is a feature planned that will enable grouping components into (let's say) trees?
Attachments (2)
Change History (7)
by , 16 years ago
| Attachment: | trac 01 admin components.jpg added |
|---|
by , 16 years ago
| Attachment: | trac 02 view ticket.jpg added |
|---|
comment:1 by , 16 years ago
| Summary: | Components (inside the ticket system) should be accessible through the wiki. → Components [ticket system] should be accessible through the wiki (see attachments) |
|---|
comment:2 by , 16 years ago
follow-up: 4 comment:3 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
There is no explicit tie between the wiki and ticket systems. If you want to make wiki pages for them, you are certainly able to, but you are implying those additional semantics, not Trac. You are correct in that we should remove the description field or find a way to show it to the user though. I'm sure there is a separate ticket about that somewhere.
comment:4 by , 16 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
Replying to nkantrowitz:
There is no explicit tie between the wiki and ticket systems. If you want to make wiki pages for them, you are certainly able to, but you are implying those additional semantics, not Trac. You are correct in that we should remove the description field or find a way to show it to the user though. I'm sure there is a separate ticket about that somewhere.
Now that you acknowledge there's an issue, either:
- close as duplicate, taking the time to find the actual original ticket
- if there's none, keep that ticket as a reminder to fix the issue
But closing as wontfix doesn't make sense.
by the way: what's the point of adding descriptions to components?
where can i read it? am i missing something? ;)