devinhedge schrieb:
> Is there a How-To someone could point me to that walks through (step-
> by-step) importing CVS files into Agilo on Trac? I've seen a lot of
> people talking about it, but no documentation to speak of.
So far there is no real how to but just by chance we wrote some
documentation for the integrated Agilo help. I'm pasting this just here,
I hope you don't mind that it uses wiki syntax:
=== Managing tickets via CSV files ===
Agilo gives you the possibility to do some "bulk" operation, by editing
multiple tickets at the same time, in a CSV file (e.g.: you can use
Excel and export in CSV) to speed up some common tasks, like for example
uploading a set of tasks written down during a Sprint Planning meeting,
without having to type it in one after the next.
The CSV format to use is very simple, the first row of the CSV file must
contain the ''property name'' of the ticket, you can get a sample one,
by creating a [/query custom query], choosing the columns you want to
modify, and clicking on the ''Comma delimited text'' at the bottom of
the page. The generated file will be editable, in case you don't want to
change a specific column, you will just have to prepend an '_' to the
column name, that would do. For example, if you download the CSV from
the Agilo query page, than you can "hide" the {{{summary}}} column from
being considered by the CSV Importer, by renaming it to {{{_summary}}}.
Please note that you have to use the 'internal' attribute name instead
of the label used for display purposes (e.g. use 'rd_points' instead of
'User Story Points'). As an administrator you can see the internal names
in the [/admin/agilo/fields Field Admin].
The current import/modify routines don't modify linking of tickets
(yet). Also there will be no email notifications if you change a ticket
via CSV. Feel free to send patches to implement this :-)
Agilo allows you to:
- '''Import''': new tickets from a CSV file, in which case you won't
need the ticket number - will be ignored anyway - because new tickets
will be generated. Be aware that Agilo makes no check on existing ticket
summary or similar properties, the only unique identifier is the ticket id.
- '''Modify''': modify existing tickets in a bulk way, by exporting
tickets first (using the [/query custom query] for example) and by
changing specific properties. Be aware that in this case there should be
either a column named {{{id}}} or a column named {{{ticket}}}.
- '''Delete''': delete existing tickets from the system. The delete
will be possible only with the {{{TICKET_DELETE}}} permission. In case
of delete the only needed information will be the ticket ids.
In order to facilitate the bulk functions, Agilo shows you a preview
before completing every operations, where you will be able to see if the
import data have been correctly interpreted by Agilo, and in case of
special characters, also try with different encoding. Agilo will try to
guess the encoding from the file, but it is not always successful, so it
may need your help. If the data shown in the preview are ok, then you
can '''Confirm''' the import and ticket will be created, modified or
deleted (depending on which action you chose).
If you have more questions, feel free to ask :-)
fs
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
-~----------~----~----~----~------~----~------~--~---
