Using the Issue Tracker
The issue tracker manages reports of technical problems (i.e., potential "Bugs" 
Image Added) and requests for future enhancements (i.e. improvements 
Image Added) concerning the program. In contrast to points of discussion in the Forum, issues are items that require a developer to revise the code of the program. To avoid unnecessary redundancy in bug reports, please follow the following steps to report your issue:
C.1 Check To Do List
Before reporting an issue, please first check for similar reports and in case leave a comment at the corresponding ticket (i.e., "BARNA-XXX"). A known issue can be OPEN, for example if the described scenario has not yet been confirmed and/or if the priority is low, or marked IN PROGRESS if a developer is already working on a solution. In either case, you might leave a comment at the corresponding report to help the developers in reproducing and prioritizing the issue correctly.
Known Bugs
| Jira |
|---|
| server | Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = BARNA AND type = Bug AND component = Astalavista AND status not in (Closed, Resolved) statusCategory = "To Do" ORDER BY lastViewed |
|---|
| serverId | a3e698dc-c3cb-3dd9-968b-0cacbbff90d5 |
|---|
|
Submit a new Bug
Recently Closed Bugs
C.2 Review Done Issues
If there is no report of an unresolved issue similar to the scenario you are experiencing, please further skim the RESOLVED tickets for possible workarounds or problems that were not satisfactorily resolved. Moreover, there can exist issue reports that have been CLOSED without providing a solution, for instance if the issue describes a scenario that is not an error respectively not a desirable improvement, or where the solution is not done through changes in the code (i.e., "Won't fix").
| Jira |
|---|
| server | Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = BARNA AND type = Bug AND component = Astalavista AND status in (Closed, Resolved) statusCategory = Done ORDER BY lastViewed |
|---|
| serverId | a3e698dc-c3cb-3dd9-968b-0cacbbff90d5 |
|---|
|
C.3 Report an Issue
If there is a report similar but not identical to the scenario you are experiencing, or if there is no known issue that matches your observations, you should create a new ticket describing your request.
 Image Added
| Project | Barna Package (BARNA) |
|---|
| Issue Type | Bug or Improvement (Stories and Epics are created by developers when connecting atomary issues) |
|---|
| Summary | a short and concise outline of the reported scenario |
|---|
| Components | Astalavista |
|---|
| Affects Versions | the version of the program where the issue was observed, leave blank if unsure |
|---|
| Description | the steps to reproduce the issue, including a copy of the command line if appropriate (larger files can be attached to the ticket after creation) |
|---|
C.4 Issues Created from Forum
...
Threads
| Anchor |
|---|
| IssuesFromDiscussions |
|---|
| IssuesFromDiscussions |
|---|
|
Below some issues that have by mistake been reported in the discussion forum.