Getting started – Jira Cloud¶
Live check in progress
The Cloud views use the same model as Data Center and the format of working Structure Cloud views (Markdown, emoji bars) and, for native columns, the official Structure Cloud API. A full check on a live Cloud instance is still open (Fix Versions as formula variable, Team and PI field types). Please report what you find.
1. Prepare Jira and Structure¶
- Fields on the Epic: Team, Story Points (or Story point estimate) and PI (single select with the PI names).
- Structure: create a structure that inserts the Epics of your area (JQL) and adds their child issues. Do not add filters.
- PI-Cap is read from the global Notes field of the team row; the generated view contains the Notes column as “PI-Cap”.
2. Generate the views¶
Open the builder, choose Jira Cloud and enter the field ids. The field
types are needed on Cloud; the builder's field helper reads them from
https://<your-site>.atlassian.net/rest/api/2/field.
3. Bring the views into Structure¶
Push (recommended): in the builder's step 6, enter an API token (Structure → personal settings → API tokens), the region of your Structure data and optionally the structure id. The builder creates the views through the official Structure Cloud API and can set the full view as default view. The API cannot change views, so each push creates new ones – delete old versions in Structure.
Or import cloud-pi-view.json and the management views by hand.
Command line:
export STRUCTURE_TOKEN=… # Structure API token
python3 -m foreca3t --config foreca3t-config.json --push --region eu --structure 123
4. Group¶
The quick transformations are the same as on Data Center.
Differences to Data Center¶
| Data Center | Cloud | |
|---|---|---|
| Colours and badges | Wiki Markup | Markdown (:panel) |
| Plan vs Actual bar | coloured blocks | emoji squares |
| PI-Cap | Notes type column | global Notes field |
| Bring into Structure | import | push via API, or import |