How do I use the issue tracker

This article will help you submit problems, questions, and recommendations in the issue tracker.

To submit a Defect (bug), Question, or a New Feature/Recommendation:

• Login to the your imPowr website.

• Go to the System menu.
• Click on the Issue Tracker form in the IT Management section .
• Select New Issue.

• Add an issue Title.
• Enter the Form or Area of the System where the change is needed (when on the page where the error is occurring, look at the URL and you should see something.aspx. That is the area). If the area is not known, leave “Not Specified”.
• Select the issue Category (Documents, Functionality, Images, Look & Feel, Notifications, Performance, Security Rights, or Usability). If the category is not known, leave this field as “Not Specified”.
• Select the Type of issue (Not Specified, Defect, Documentation, New Feature, or Other). The system defaults to “Defect”. If the type of issue is not known, leave this field as “Not Specified”.
• Enter a detailed Description of the issue (if you followed a specific path or steps and got to an error, please enter that information). If possible, please copy and enter the page URL (the text at the top of your browser) as well.
• You may optionally paste small screen captures into the body of the text and perform other formatting much like you would if you were using Microsoft Word.
• Press “Save” to submit the issue to Continual Care Solutions’ Support Team.

Defect (bug), Question, and New Feature / Recommendation guideline:

Title

• The Title of the defect, question or new feature request should be as concise and crisp as possible.

Example:

[Backlogs] Grey out status fields in task board which cannot be used by role

Description

• The defect, question, or new feature description should be concise and expressive.
• Mention the reason why the fix or change is relevant. Describe the associated use case.
• Add acceptance criteria for clarification.
• Describe the current behavior if it is to be changed by the request.
• Using the following (user story) format, describe the intent behind a new feature request:

Example:

_ I only want to see the statuses which are Active, so I know which ones I can use, before I select them._

Acceptance criteria

• State and detail the requirements in the acceptance criteria.

Example:

• In the task board only show the status allowed for the role the user has in the project as active.
• The status fields which are inactive should have e.g. a grey background to make clear that a user cannot use them.

Current behavior

• If the feature request is changing existing behavior, briefly explain the current behavior.

Example:

Currently, all status transitions set for a type are displayed as active (independent of the allowed status transitions defined by the workflow).

Drawings / Screenshots

• If the request is visual, it is helpful to add a small drawing or a screenshot highlighting the issue or desired changes.
• The drawing or screenshot can be pasted into the description of the issue, using programs such as Microsoft Paint or Microsoft Snip & Sketch

Example of a defect issue:

**Example of a New Feature / Question / Recommendation: **