ASAP - The Aptana Issues Tracker

JIRA - Local help

JIRA tracks issues, which can be bugs, feature requests, or any other tasks you want to track.

Each issue has a variety of associated information including:

  • the issue type
  • a summary
  • a description of the issue
  • the project which the issue belongs to
  • components within a project which are associated with this issue
  • versions of the project which are affected by this issue
  • versions of the project which will resolve the issue
  • the environment in which it occurs
  • a priority for being fixed
  • an assigned developer to work on the task
  • a reporter - the user who entered the issue into the system
  • the current status of the issue
  • a full history log of all field changes that have occurred
  • a comment trail added by users
  • if the issue is resolved - the resolution
Issue Types

JIRA can be used to track many different types of issues. Below are the types configured in your system. More can be added from the administration section.

For Regular Issues
Bug
A problem which impairs or prevents the product from functioning properly
Enhancement
A new feature or an improvement of an existing feature
Modification
Changes to the defualt configuration of a cloud instance
Question
A question that's not a bug and not an ehhancement
Task
A task that needs to be done.
For Sub-Task Issues
Sub-task
A sub-task of the issue
Priority Levels

An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels at the administration section.

Critical
Crashes, loss of data, severe memory leak.
Major
Major loss of function.
Average
Minor loss of function, or other problem where easy workaround is present.
Low
Cosmetic problem, low impact corner case
Unprioritized
Not yet assigned a priority
Statuses

Each issue has a status, which indicates the stage of the issue. In the default workflow, issues start as being Open, progressing to In Progress, Resolved and then Closed. Other workflows may have other status transitions.

Open
The issue is open, but may not have been reviewed yet
In Progress
This issue is being actively worked on at the moment by the assignee.
Reopened
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
Resolved
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Reviewed
The issue has been reviewed by Aptana
Awaiting User Response
The issue requires more information from the reporting user to proceed.
Triage
Enable Support to filter issues before assigning to Engineering
Accepted
The issue has been opened to a developer, who has agreed to work on it for the target release.
New
New bug; needs review/triage.
Resolutions

An issue can be resolved in many ways, only one of them being "Fixed". The defined resolutions are listed below. You can add more in the administration section.

Fixed
A fix for this issue is checked into the tree and tested.
Cannot Reproduce
All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
Not an Issue
Reported but turns out to be misunderstanding of product or due to non-Aptana software
Duplicate
The problem is a duplicate of an existing issue.
Need Steps to Verify
Fixed status cannot be verified, instructions to reproduce are required
Incomplete
The problem is not completely described.
Won't Fix
The problem described is an issue which will never be fixed.
Obsolete
Feature is obsolete
Answered
Not a bug or an ER, just a question -- and it's been answered.