Edgewall Software

Ticket #4044 (closed enhancement: duplicate)

Opened 2 years ago

Last modified 21 months ago

new ticket optionally uses templates too

Reported by: ThurnerRupert <rupert.thurner@…> Owned by: jonas
Priority: normal Milestone:
Component: ticket system Version: devel
Severity: normal Keywords:
Cc:

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

Change History

Changed 2 years ago by cboos

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.

Changed 2 years ago by ThurnerRupert

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?

Changed 21 months ago by cboos

  • milestone set to 1.0

One alternative would be to start from "typical" tickets and clone them, as proposed in #4686.

Changed 21 months ago by ThurnerRupert <rupert.thurner@…>

  • status changed from new to closed
  • resolution set to duplicate

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" ....

Changed 21 months ago by cboos

  • milestone 1.0 deleted

Add/Change #4044 (new ticket optionally uses templates too)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
to The owner will change from jonas. Next status will be 'closed'
 
Note: See TracTickets for help on using tickets.