Testing & User Feedback process

Owned by Abi James
Last updated: Oct 14, 2016
4 min read

In order to capture feedback on SlideWiki, we have created a separate JIRA project SlideWiki Acceptance and Quality SWAQ. This is open to all SWIK users. Members of the public (SlideWiki users) can also create issues within the SWAQ project directly using 2 methods. 

Instructions to SlideWiki users for providing feedback

Want to tell us something about SlideWiki? We really welcome any suggestions or ideas your have! And if you discover a problem we are keen to fix it as soon as possible.

There are two ways you can send us feedback.

Method 1: Use the feedback Button

On each SlideWiki page you will see a Feedback button on the right-hand side. Simply click the button and complete the form.


We ask you to provide a short summary and a description. Use the Attach file option if you are able to take a screenshot. If you provide us with your name and email address then we can keep you up to date with developments on SlideWiki and contact you if we need further information relating to your feedback.

Method 2: Email your feedback to jira@slidewiki.atlassian.net

If you have general feedback about SlideWiki or are unable to access the feedback button then you can email us at jira@slidewiki.atlassian.net. Please tell us what you are trying to do on SlideWiki and if possible provide the URL and attach a screenshot.

Instructions to SlideWiki developers for capturing bugs

If you encounter a bug or issue with SlideWiki then please use the JIRA Capture tool. If you do not have this installed go to the Capture menu in JIRA. 

If a bug/issue is related to an existing task in SWIK then select "Attach to existing issue" and enter issue key. New issues should only be created in SWIK if they have a user story and task defined.

All other bugs should be entered into the SWAQ project. 

Please ensure you make it clear if this bug is on the live server (stable.slidewiki.org) or on the experimental server (when there is likely to be an open task on SWIK).

If you identify a bug and you know the developer that has worked on this code then add a comment and mention them so that they are aware this has been logged. But do not allocate it to them. If the developer is able to define the task to address the bug, they should create this in SWIK.

Process for reviewing feedback in SWAQ

An issue created by a users is added to SWAQ as an open task and displayed in the "Reported" column of the Testing & Feedback board.  

A member of the SlideWiki development team then needs to evaluate the issue. This should be undertaken by someone who has not been directly involved with developing the feature. At the start of the evaluation the task should be allocated to the JIRA user and its status changed to in-progress.

The evaluation should first decide if the issue is reporting a bug (Bug), suggestions for improving an existing feature or user story (Improvement), a new user story (User story) or general feedback (Feedback) and alter the Issue Type appropriately. Use JIRA Capture to gather screenshots and notes on the issue. If the issue is a Bug or then the evaluator should attempt to reproduce the issue. Add additional comments to the issue if required and particularly if you were unable to reproduce the bug. Add labels and components to the issue as appropriate (the component list matched the SWIK project.

Once a the evaluation is complete, it should be either:

  • Allocate to development (FOR DEVELOPMENT). This means a task should be created or updated in SWIK in order for the development team to work on in the near future. This will be undertaken during sprint retrospectives/planning
  • Future review (ON HOLD). This means that the issue is valid and should be considered for future development tasks. 
  • Done (RESOLVED, CLOSED). This means the task requires no further work, for example if it is a duplicate of an existing issue on SWIK task or is not valid.

If the issues are moved to the appropriate columns using the board, then the workflow will be automatically updated.