Skip to end of metadata
Go to start of metadata

Using the Issue Tracker

The issue tracker manages reports of technical problems (i.e., potential "Bugs" ) and requests for future enhancements (i.e. improvements ) 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. In doubt, refer to the list of issue reports that were originally posted here the wiki and have then been transferred to the issue tracker.

 


Issues can be viewed anonymously, but creating a new issue or commenting on an existing issue requires the user to sign up and log into the issue tracker. Contact the site administrators if there are problems during registering or submitting a ticket.


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.

key summary type created updated due assignee reporter priority status resolution

com.atlassian.sal.api.net.ResponseStatusException: Unexpected response received. Status code: 503

View these issues in Jira

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 marked "resolved" without providing a real 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").

key summary type created updated due assignee reporter priority status resolution

com.atlassian.sal.api.net.ResponseStatusException: Unexpected response received. Status code: 503

View these issues in Jira

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. Sign in or sign up for using the issue tracker, go to the issues of the BARNA project and press the "Create" button (top bar) to invoke the issue creation dialogue.

ProjectBarna Package (BARNA)
Issue TypeBug or Improvement (Stories and Epics are created by developers when connecting atomary issues)
Summarya short and concise outline of the reported scenario
ComponentsAstalavista
Affects Versionsthe version of the program where the issue was observed, leave blank if unsure
Descriptionthe steps to reproduce the issue, including a copy of the command line if appropriate (larger files can be attached to the ticket after creation)

Issues Created from Forum Threads 

Below some issues that have by mistake been reported in the discussion forum.

  • No labels