Eventum

From CTRNet Wiki
Jump to: navigation, search

The CTRNet development team uses Eventum for issue tracking. The system is hosted on our development server and is only available to members of the CTRNet development team.

Banks that choose to participate with the CTRNet team are welcome to create their own projects within the system to manage local issues as well as view outstanding CTRNet issues.

Contents

Priority Levels

We have defined four priority levels for Eventum items:

  • Critical - Bug fix or issue that requires immediate attention. First items addressed when working on fixes. Scheduled for release at next minor version or as it's own release depending on severity.
  • High - Issue scheduled for next minor/major release.
  • Medium - Upcoming features and minor bug fixes that don't impact user functionality. Will be upgraded to 'High' when scheduled for release in the next minor/major version.
  • Low - Ideas, issues or suggestions that may or may not be implemented. May be killed or suspended.

Adding New Issues

When creating a new issue in Eventum select the appropriate priority level and category. Categories are defined as:

  • BUG - Functionality that is broken or yielding unexpected results.
  • CHANGE - Updates to existing functionality or form layout.
  • ENHANCEMENT - New functionality, fields or complete forms.

Be sure to select the appropriate module! The status field should be set to 'Discovery' for all new issues.

Issue Status

Eventum has four default statuses for issues. They are:

  • Discovery - All new issues begin at this stage. This indicates an item has been reported but no action has been taken.
  • Requirements - Issue requires further discussion, clarification, or information to complete implementation by a developer.
  • Implementation - Issue is actively being worked on.
  • Evaluation and Testing - A solution or new feature/change has been implemented on the development site. Testing and validation required.

Once an issue has been sufficiently tested the issue should be closed by the original reporter.

Best Practices

Following these guidelines will help us best locate and correct any bugs/issues found in the system:

  • Upload screenshots (in some type of image format) whenever possible! A picture can save you writing paragraphs of descriptive text. Eventum allows you to upload three files at a time. (2MB file size maximum)
  • Provide a URL to the online development site if applicable or a step-by-step process to replicate the issue. This gives the reviewer quick access to a live example of your particular issue. If not possible, a series of steps or good description on where the issue occurred.
  • Finally, keep track of your issue! Eventum will automatically generate emails when an issue is updated, notes left, or status changed.
Personal tools