...
The summary field is a high level description of the WHAT needs to be resolved. Consider your audience, the summary needs to clearly and succinctly detail the feature or issue from the user's perspective.
General guidelines for Summary
Templates. If functionality change, use user story template (see below). If bug fix, use bug fix template (see below)
Describes the issue from a behavioral perspective (i.e. no implementation details)
Understandable for most audiences, e.g. customer, users, stakeholders
Content should be professional in nature
User Story Template
As a <type of user>, I need <some goal>, so that <some reason>
- For features or new functionality, use the user story template for the summary
- User stories provide context to the person working the ticket
- User stories communicate the value of the ticket
- DDF generally uses the following roles: User; Administrator; Integrator
Bug Fix Template
<Symptom> due to <Cause> [, forcing user to <workaround>]
...