Difference between revisions of "Resources/Issue tracker"
(→Description: Added a more detailed account of what we'd like to see in bug descriptions.) |
|||
Line 35: | Line 35: | ||
==Description== | ==Description== | ||
− | Helpful information to include in the Description field are the steps to reproduce the bug or behaviour you are experiencing. | + | Helpful information to include in the Description field are the steps to reproduce the bug or behaviour you are experiencing. For us to be able to best diagnose any bug reported, other developers will need to be able to reproduce it. Our preferred method for bug reporting uses a 3-part description, as follows: |
+ | |||
+ | '''To reproduce:''' | ||
+ | |||
+ | Outline the exact steps required for someone else to recreate your bug. You can assume the reader will be familiar with the application, but you should still ensure your instructions to reproduce are clear and detailed. For example: | ||
+ | |||
+ | ''1. Log in as an administrative user'' | ||
+ | ''2. Navigate to Browse > Archival descriptions'' | ||
+ | ''3. Click on the "Level of description" facet for Item'' | ||
+ | |||
+ | '''Error encountered:''' | ||
+ | |||
+ | What happens when you perform the steps described above? Include any details you think are relevant. If you think it will be helpful, you can take a screenshot of what you are seeing and attach it to the issue ticket. | ||
+ | |||
+ | Example: | ||
+ | |||
+ | ''Results list displays items, series, and files. See attached screenshot.'' | ||
+ | |||
+ | '''Expected result:''' | ||
+ | |||
+ | Describe to us what *should* have happened at the end of the initial steps to reproduce; what you would expect to happen if the application was responding properly. For example: | ||
+ | |||
+ | ''Archival description browse list results should be limited only to records whose level of description is "Item." | ||
+ | |||
+ | '''Notes''' | ||
+ | |||
+ | Not always necessary, but if there are other details that will help us, please share! What have you already tried to troubleshoot the problem? What browser were you using, and did you try to repeat the error on a different browser (or after clearing your browser cache)? Were you or your system administrator able to reproduce the problem while in Debug mode? If so, please save the stack trace (e.g. error message you see) and attach it to the issue! Is there anything particular about your installation that might be causing or affecting the bug, that we should know about? Have you added custom code to your application that is not included in a public release? | ||
+ | |||
+ | Anything that might help us better diagnose the problem - let us know. | ||
==Status== | ==Status== |
Revision as of 17:49, 4 July 2014
Main Page > Resources > Resources/Issue tracker
Artefactual uses Redmine project management software to track bugs and issues in AtoM. You can find our Redmine instance at https://projects.artefactual.com
Contents
Register for an account
You can register for an account in Redmine at: https://projects.artefactual.com/account/register
If you are a client of Artefactual, you likely already have an account. Email support@artefactual.com if you need assistance.
Search for a bug or issue
Anyone can search Redmine for an existing issue or bug. Visit https://projects.artefactual.com and enter your search keywords.
You can also browse AtoM issues here: https://projects.artefactual.com/projects/atom/issues
Note that issues or bugs related to client-specific development will not appear if you are not logged in, and further if your account is not associated with that project.
Create a new bug or issue
1. Always search Redmine for an existing bug or issue before reporting a new one.
2. To create a new bug or issue, navigate to the AtoM project by clicking on "Jump to a project" and then "AtoM".
3. Click on "New Issue" and fill in the required fields as outlined below:
Tracker
Choose "Bug" for an issue with an existing feature, or "Feature" to suggest a new functionality to AtoM.
Subject
Provide a brief description of the bug or feature you are requesting.
Description
Helpful information to include in the Description field are the steps to reproduce the bug or behaviour you are experiencing. For us to be able to best diagnose any bug reported, other developers will need to be able to reproduce it. Our preferred method for bug reporting uses a 3-part description, as follows:
To reproduce:
Outline the exact steps required for someone else to recreate your bug. You can assume the reader will be familiar with the application, but you should still ensure your instructions to reproduce are clear and detailed. For example:
1. Log in as an administrative user 2. Navigate to Browse > Archival descriptions 3. Click on the "Level of description" facet for Item
Error encountered:
What happens when you perform the steps described above? Include any details you think are relevant. If you think it will be helpful, you can take a screenshot of what you are seeing and attach it to the issue ticket.
Example:
Results list displays items, series, and files. See attached screenshot.
Expected result:
Describe to us what *should* have happened at the end of the initial steps to reproduce; what you would expect to happen if the application was responding properly. For example:
Archival description browse list results should be limited only to records whose level of description is "Item."
Notes
Not always necessary, but if there are other details that will help us, please share! What have you already tried to troubleshoot the problem? What browser were you using, and did you try to repeat the error on a different browser (or after clearing your browser cache)? Were you or your system administrator able to reproduce the problem while in Debug mode? If so, please save the stack trace (e.g. error message you see) and attach it to the issue! Is there anything particular about your installation that might be causing or affecting the bug, that we should know about? Have you added custom code to your application that is not included in a public release?
Anything that might help us better diagnose the problem - let us know.
Status
Leave as New.
Priority
Please leave at Medium. Artefactual staff will receive triage the bug or feature as appropriate.
Other fields
Please leave blank and Artefactual staff will update as appropriate.