Prefill issue form with the template provided in the "Issue summary standards" article.

i agree, this should definitely not be hard coded into issue.inc. if there's interest for adding support for an admin setting for "default issue body", that would be worth doing. however, project should be much more generic in terms of the kinds of projects it's designed to handle.

for example, on my live drupal site, i have a project for "[site] issues" so that users of the site can submit bug reports and feature requests about the site itself (which sometimes involve just changing settings, sometimes adding new modules, sometimes fixing or extending existing modules, etc). lots of the time, i'm the one creating the issues, and it's just my own todo-list manager, but even in that case, other people can comment on my ideas, bump their priority, whatever (i love drupal).

if i can ever convince the people at my day job to switch to using drupal for everything, we'll be making major use of the project module. our projects aren't web-based applications at all, and fields like the DB or PHP versions would be meaningless. they'd be similarly meaningless even on drupal.org for documentation or translation issues (from what i can tell).

i already have concerns about how project is setup to require a cvs repository and "releases" of the project (see http://drupal.org/node/19243 for other input on this). that's specialization and complexity that should be handled either via settings or add-on modules/plugins to project, not behavior that's enforced on all uses of project.module.

thanks,
-derek

#400702: Pre-fill new bug reports has been marked as a duplicate

Here: Issue summary standards