Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The timeline view lets you represent data in a chronological order.

...

Timeline views need two accept these configuration fields:

dateStartField (string, required)

...

Info

Dates need to be supplied in the ISO 8601 format, YYYY-MM-DD. For example: 2022-04-07

groupFieldKey (string, optional)

Defines over which field the rows should be grouped. Consider the following section data:

Code Block
{
  "data": {
    "Begin": "2022-04-07",
    "Components": "Configuration"
  },
  "name": "Configure Sources",
},
{
  "data": {
    "Begin": "2022-04-07",
    "Components": "Infrastructure"
  }
  "name": "Configurate SSL-Certificates"
},
{
  "data": {
    "Begin": "2022-04-10",
    "Components": "Infrastructure"
  }
  "name": "Install Binaries"
}
{
  "data": {
    "Begin": "2022-04-01",
    "Components": "Infrastructure"
  }
  "name": "Setup Environment"
}
{
  "data": {
    "Begin": "2022-04-08",
    "Components": "Infrastructure"
  }
  "name": "Assign Roles"
}

If you wanted to group rows that have the same value in the Components field, you could add a groupFieldKey with the value Components, and the timeline will group rows that belong together:

...

groupStyle (enum, optional)

Can be either set to expandable (default) or merged. If set to expandable, groups will have a label with a button and the group can be expanded/collapsed (see screenshot above). If set to merged, the groups will be merged to a single swim lane. This is only recommended if there is no overlap between any items inside a group.