Before requesting a new feature,
|
Summary description of the feature requested in the format of “As [role] I request [feature]” (The roles typically used in ArchivesSpace are System Administrator, Repository Manager, Project Archivist, Archivist, Advanced Data Entry Staff, Beginning Data Entry Staff, and Repository Patron)
Examples: |
A detailed description of the desired functionality
Feature requests that include detailed Behavior Scenarios or Use Cases are more likely to be prioritized for development since these use cases provide more detailed information about the requested feature and improve the likelihood of a successful outcome in development.
Requesters are encouraged to submit a feature request using the Given/Then/When format.
Feature requests that follow the requested Given/Then/When format or that include detailed specifications and descriptions are more likely to be selected for development. |
Ticket submitters and all other individuals interested in the development of the feature request are encouraged to remain vigilant of the ticket and respond to all requests for information. Tickets that have a status of "awaiting more information" are unable to be prioritized or implemented. |