= Backlog Administration =
[[PageOutline]]

Agilo introduces a special Backlog concept, and allows you to configure as many Backlog as you like to suite your needs. By default Agilo creates in every projects two main Backlogs:
 - The [agilo-help:scrum/ProductBacklog Product Backlog] where the Product Owner stores and manage the [agilo-help:scrum/Requirement Requirements] and the [agilo-help:scrum/UserStory User Stories]
 - The [agilo-help:scrum/SprintBacklog Sprint Backlog] where the Team manages the daily work during every Sprint

In Agilo every '''Backlog''' can be bound to a specific time-interval as well as being a ''Global'' Backlog that collects all the tickets into the system, independently from the fact that they have been planned for some [agilo-help:scrum/Release Release] or [agilo-help:scrum/Sprint Sprint].


== Backlog Administration Panel ==

Located in [/admin/agilo/backlogs Admin/Agilo/Backlogs]

If you click on the '''Admin''' icon [[Image(/chrome/agilo/images/icon.admin.png, border=0, width=16, height=16)]] on the top toolbar of agilo, you will enter the Admin interface. Under ''Agilo'' you will find a ''Backlogs'' menu item, that will lead you to the main page for the Backlogs administration.


=== Adding a new Backlog Type ===

If you want to add a new Backlog, just type the new ''Backlog Type'' name in the ''Add Backlog'' form, and press the button '''Add and edit'''. You can reach the edit page also simply by choosing an existing backlog type.


=== Edit an existing or a newly created Backlog ===

In the edit page of the Backlog Administration panel, you'll find some property fields to set, some of them are dynamically bound with each other to make the configuration of the backlog easier:

 - '''Description''': enter here the description of the Backlog and what it is supposed to contain. You can use Wiki syntax here.
 - '''Scope''': the scope of the backlog defines if the backlog has to be bound to a specific time interval (represented by a Milestone or a Sprint) or has to be a ''global'' backlog, which means that it will load all the tickets of the defined type which are entered in the system:
    - ''global'': loads all the tickets from the system which belong to the chosen types, if the '''strict''' option is specified only the tickets which are not specifically planned for a ''Sprint'' or ''Milestone'' are loaded 
    - ''milestone'': loads all the tickets from the system which belong to the chosen types and are planned for a specified milestone (in the user interface these types of backlog are always shown with a pull-down menu where the user can choose a specific scope: milestone or sprint). Note that also all the tickets not explicitly planned for a milestone or sprint and linked to tickets which are planned are loaded as references
    - ''sprint'': same as milestone but applied to a Sprint
 - '''Available Charts''': should show only the charts that can be combined with the backlog ''scope'' you have chosen. For example the [agilo-help:scrum/BurndownChart Burndown Chart] can be shown only in combination with a ''sprint'' scope. you can choose one or more charts, which will be shown in the backlog view on top of the backlog ticket list
 - '''Ticket Types''': here you can choose multiple ticket types to show in your backlog, keep in mind that they will be sorted according to the hierarchy only after you explicitly click the ''Default Sorting'' button
 - '''Column Preferences''': here you can choose the ''columns'' or properties for a ticket that you want to see in the Backlog view. For each column you can choose if that could also be ''editable'' (means that if the current user of the backlog view has the rights to edit a specific ticket, will see the defined columns as editable properties). The ''Alternative'' column, allows you to choose and alternative column to show in case a ticket type loaded doesn't have the property you are editing. In this column you can see also the [agilo-help:admin/TypeAdmin#CalculatedProperties calculated properties] which are not editable but can be used to show aggregated values on parent types (e.g.: the `remaining_time` in a Sprint Backlog can be replaced by the `total_ramaining_time` in stories). The ''Sorting'' column let's you choose if the current ticket property should be used also as a sorting key for the default sorting as well as the sorting order (i.e.: Ascending or Descending). The default sorting will perform a stable sorting on the backlog tickets, following the order of the keys, this can be set explicitly changing the column ''Order'' which is not only reflecting the order in which the column are shown but also the order in which they are evaluated for the sorting.
