#4044 closed enhancement (duplicate)
new ticket optionally uses templates too
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
it would be beneficial if one could choose a ticket description template out of a list when creating a new ticket, like it will be possible for wiki pages via PageTemplates.
Attachments (0)
Change History (5)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
this would look nice i guess … but more complicated to implement, isn't it?
somehow it would be anyway nice if you may choose out of multiple templates for a type. this would allow to have type "task" and put change requests, meeting and minutes, etc in tickets.
for bugs and enhancements i'm not sure if it exists that you have different default contents depending on your component and priority.
maybe a "basic v1" and a "more complex v2" would make sense?
comment:3 by , 18 years ago
Milestone: | → 1.0 |
---|
One alternative would be to start from "typical" tickets and clone them, as proposed in #4686.
comment:4 by , 18 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
you r right, cloning would be even better … if there would be some possibility to choose one to clone for the new user entering a ticket.
close this as "inferior" ….
comment:5 by , 18 years ago
Milestone: | 1.0 |
---|
If so, that should be linked to the ticket type choice, don't you think?
It doesn't make sense to first select the type, then select from different "templates". I think that there should be one default description associated to each type. Switching the type should change the description content "on the fly", but only if it had not been already modified or if it's empty.