INDEX
Overwrite of existing stickies
If you want to update existing sticky-notes by doing second csv-import, you need to make sure that the stickies have an ALM-key set. If you do not have an alm-key set for the sticky, it will create a duplicate instead of updating.
File format
Following column separators are permitted for imported files:
| Name | Character |
|---|---|
| comma | , |
semicolon | ; |
| colon | : |
tab | \t |
pipe | | |
Program Backlog Board
Your data has to be CSV UTF-8 formatted in the following table style:
| board-type | sticky-type | text | alm-issue-id | WSJF |
|---|---|---|---|---|
backlog | Feature | This is a text for a certain Feature | RT-100 | 1 |
| backlog | Enabler | This is a text for a certain Enabler | RT-101 | 2.6 |
| backlog | Enabler | This is a text for a certain Enabler-2 | RT-102 | 3 |
Download a template here: backlog-board.csv
Columns explained
- board-type: Has to be backlog if you want to import it to the backlog-board
- sticky-type: Has to be one of the names you gave a sticky-type of the backlog board (in setup.piplanning.io)
- text: Text which is displayed on the sticky-note
- alm-issue-id: (can be empty, but column has to exist); If an existing sticky-note on the board already has the same alm-issue-id, it will update the other properties of this sticky (instead of creating a new one)
- WSJF: WSJF-value displayed on the sticky-note
Team Boards
Your data has to be CSV UTF-8 formatted in the following table style:
| board-type | team-name | sticky-type | text | alm-issue-id | story-points | iteration-number |
|---|---|---|---|---|---|---|
| team | API | Story | This is a text for a certain Story | RT-200 | 3 | 0 |
| team | API | Story | This is a text for a certain Stroy2 | RT-201 | 2 | 1 |
| team | Shoppers | Risk | This is a text for a risk | 2 |
Download a template here: team_template.csv
Columns explained
- board-type: Has to be team
- team-name: Has to be one of the team-names attending this session. Make sure it matches the name given in setup.piplanning.io
- sticky-type: Has to be one of the names you gave a sticky-type of the backlog board (in setup.piplanning.io)
- text: Text which is displayed on the sticky-note
- alm-issue-id: (can be empty, but column has to exist); If an existing sticky-note on the board already has the same alm-issue-id, it will update the other properties of this sticky (instead of creating a new one)
- story-points: (can be empty, but column has to exist); Story points for this sticky.
- iteration-number: integer value: 0 matches the first iteration.