Skip to end of metadata
Go to start of metadata

The ArchivesSpace team encourages all users of the ArchivesSpace application to report any bugs encountered during use of the application. 

Before reporting a bug,

  • 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 three different ways:

1)      Directly to the Support JIRA  (select Create issue)

2)      Indirectly via the “Report an Issue” link on the ArchivesSpace website

3)      Indirectly via the “Send Feedback or Report a Problem” option appearing at the bottom of pages in the ArchivesSpace application

 

All three pathways will load a form for reporting a bug: 

 

 

An actionable bug report requires the following:

1)      Project identified as “ArchivesSpace Support (AS)”

2)      Issue Type identified as “Bug”

3)      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;

5)      Version of the ArchivesSpace application in which the problem was encountered

6)      Email address of the reporter recorded in a comment area (for the purpose of following up if necessary)

 

Optional information may be recorded as follows:

1)      A fuller description of the event, describing the steps leading up to when the problem was encountered

2)      Attached screen clips or other documents that help to explain the problem encountered.  

  • No labels