...
- determine that the bug has not already been fixed by updating to the latest release and attempt to replicate the problem in it;
- review the unresolved bugs logged in the ArchivesSpace development project to see if the bug has already been reported, in which case you can indicate in the report that you also encountered the bug; and, if desirable,
- post a message to the ArchivesSpace Users Group list, asking for help in understanding and verifying the bug you encountered. You will need to be staff of an ArchivesSpace member organization.
Once you have decided to file a bug report, you may do so in one of two ways:
1) Directly to the Development in 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:
in many installations. If that link is not there or not pointing to the current address, go directly to JIRA and select Create to create an issue, as in #1.
An actionable bug report requires the following:
1) Project identified as “ArchivesSpace Support (AR)”2) Issue Type identified as “Bug”
32) Summary description of the problem encountered that includes a brief statement of the problem, for example:
- Component order shifts after edit and save;
- Wrap and tag editor does not work;
- Resource title displays with escaped characters;
53) Version of the ArchivesSpace application in which the problem was encountered
...
Optional information may be recorded as follows:
...