(If you want to report a bug, see How to Report a Bug.)
The ArchivesSpace community encourages requests for new features to be added to the ArchivesSpace application. New features can increase the application’s suitability for supporting management of archival materials, as well as optimize the experience of the application’s users.
...
| Note | ||
|---|---|---|
| ||
Before requesting a new feature, |
...
|
...
|
Once you have determined the feature does not already exist in the application
...
1) Directly to the Development JIRA (select Create issue)
2) Indirectly via the “Send Feedback or Report a Problem” option appearing at the bottom of pages in the ArchivesSpace application
Both pathways will load a form for reporting a bug:
- Log in to your JIRA account (You will need to create a JIRA account to submit a ticket).
- Access JIRA and select Create issue (Select ArchivesSpace New Workflow as the project).
An actionable feature request requires the following:
...
...
- Issue Type identified as “New Feature”
...
Summary description of the feature requested in the format of “As [role] I request [feature]”
...
The following optional information may be recorded in the request:
1) A fuller description of the feature requested, describing any parts of it that might not be clear in the summary description
...
(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)
Info icon false Examples:
As a repository manager, I would like to link event records to name records
As a project manager, I would like the ability to declare default values comprehensively through the ArchivesSpace application
As a repository patron, I would like to be able to view a broad range of digital content within the ArchivesSpace application
...
A detailed description of the desired functionality
Feature requests that include detailed Behavior Scenarios or Use Cases can be more easily reviewed and 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.
Note icon false Feature requests that include use cases that follow the Given/When/Then format or that include detailed specifications and descriptions are more likely to be selected for development.
- Attached files, screenshots, or specifications that amplify the feature request.
Upon submission of the ticket, the Development Prioritization Council or members of the ArchivesSpace program team will contact the submitter and all other commenters directly via the ticket.
| Note | ||
|---|---|---|
| ||
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 until questions are resolved. |