Thomas Doczkal
opened 6 years ago
-
Previous Value Current Value empty 3.2.1
-
@robin GitLab for example manages templates as code.
For example there could be a directory
./.onedev-templatescontaining templates. A convention could be "Type", e.g../.onedev-templates/Bug.md. -
@mweimann thanks for the idea. Type is a custom field and OneDev does not know anything about it. I plan to implement this in global issue setting, i.e. define a template with applicable issue criterias.
-
Also it might not be a good idea to bind issue templates with repositories as:
- It requires template setup for each repository
- In future projects might be organized in tree structure and issue might be managed at a higher level covering several repositories
-
Name Previous Value Current Value Iterations
3.2.1
3.2.2
-
OneDev
changed state to 'Closed' 6 years ago
Previous Value Current Value Open
Closed
-
OneDev
changed state to 'Released' 6 years ago
Previous Value Current Value Closed
Released
Story
As a developer I want issues to have a certain structure (Template) in the description Field to request as much information as possible from the issue creator.
Background
At the moment the "Description" Field is free text and does does cover important questions. Issues do not follow a certain structure. An example could be: