Create Issue Structure Templates
|Assignee:||Jean-Philippe Lang||% Done:|
I would like a function in Redmine that would enable the creation of a group of tasks linked between them in any ways allowed by redmine in the form of a template system.
That would enable the creation of a group of task with a predefined arrangement and possibly content ( description etc..) from that template at the click of a button.
This would be extremely useful to have for managing project with templated actions (like Electronic design) which require the same steps breakdown over and over again to go to production in many different projects. Example:
If you do not have templates for these you have to copy issues or create new issues and you loose all the precedence
, relations and parenting of the group of task.
there is also a need to have automatically reoccurring tasks.
Merci d'avance Philippe :)
#3 Updated by Dominik Follmann over 8 years ago
we would be very happy about such a feature, too.
For exactly the same use-cases, as Christophe already described. Is there already a solution existing?
The current issue copy mechanism unfortunately breaks the relations within the copied structure and only creates "Copied from/to" relations.
It would be perfect, if the same relations (especially precedes,follows) would be created within the copied structure, too.
#4 Updated by Dipan Mehta over 8 years ago
Typically it is highly required that correct & identifiable information that can be followed when we are reading issues. Typically, when descriptions are vague and a long 'chat type' messaging goes on over notes for myriads of clarifications and corrections, - for anyone to take action on such issue becomes painful as the issue evolves long enough. Some may also, wish people do put correct resolution and diagnosis of solutions so as to capture the correct knowledge about the issue.
Unfortunately, in spite trying hard, I think templates of descriptions, notes don't quite work. Lazy people sometimes still leave templates as is or blank if they have such habits.
In my view, to deal with this issue very effectively is to have dedicated custom fields which becomes compulsory as the issue moves to a particular status. This, now effectively 2.1.x+ is very powerfully achievable.