= Known bugs =
The overview below visualizes the bugs found in Genius documented in the tracker and by students. I could also have used the bugtracker, but this tracker also contains bugs of the !PocketNegotiator. Before removing a bug, please ensure that it is fixed in '''all main branches'''.

== Core ==
||'''Issue number(s)'''||'''Description'''||'''Priority'''||'''Cost to fix (days)'''||
||467||AgentID is not required in actions||Low||1||
||60,72,320||Domain files and utility spaces should be checked upon repository loading||High||3||
||25,57||Implementation of real issues should be checked and fixed||Medium||3 - 5||
||449||Tournament sessions all have number one||Low||1||
||475||The session counter does not function, it always returns one||Low||1||
||-||Currently cost constrains are not generic (cost <= 900). I think it would be nice if we could set this per domain||Low||2||
||105||It is currently not possible to load a utilityspace directory, the domain is requested, which is strictly not necessary||Low||1||
||469,470||Use a (single) generic evaluation method in Utilspace instead of Evaluator||Low||10||
||468||Make an objective extend an issue||Low||2||
||31||A utilityspace can be loaded with any domain||Low||1||
||37||Objective.getSiblings overly complex||Low||1||
||38||Implementation of getType of issue seems inefficient||Low||1||
||64,67||Ensure that the type of issue matches the evaluator||Low||1||
||127||Implementation of getMaxUtility is too computationally expensive||Medium||1||
||-||A large set of todo's and fixme's (>200)||Medium||5||
||-||Trade-off agent crashes||Low||1||

== Extra features ==
||'''Issue number(s)'''||'''Description'''||'''Priority'''||'''Cost to fix (days)'''||
||461||Allow the analysis of stored negotiations by the Analytical toolbox||Low||1||
||632||GNU license||Low||1||
||-||UIAgent only works with discrete issues||Low||3||

== GUI ==
||'''Issue number(s)'''||'''Description'''||'''Priority'''||'''Cost to fix (days)'''||
||68,70,71,80,84,85,321,435,445,459,460||Creating a new scenario using the GUI is not user friendly and buggy||Medium||5 - 10||
||-||Deleting scenarios does not work||Low||1||
||-||Saving scenarios does not work||Low||1||
||-||When creating a scenario, upon exit it is not requested if you saved the scenario||Low||1||
||57||Check creating real issue domains using GUI||Low||5||
||458||Sometimes the costs in the GUI of the values of an issue are reset to zero.||Low||1||
||26||Show model gives an exception if the negotiation template file name is left empty||Low||1||