Open edtro opened 1 year ago
Added an update:
within the home/details page the documentation will be:
Added some extra possibilities to globalize the configurations (added the new -only global- section 'categories' and enabled the sections 'fields' & 'stylerules' to be set as global).
The dependency arrows will now react on the categories (the setup within the project definition or the -new- global configuration), so if a 'predecessor' is within the category 'Proposed' or 'InProgress' the arrow will indicate the relation as a blocker (=red arrow) for the successor (also optimized the arrows, so you will get less overlapping arrows).
When using the 'treeview' queries, the filter will now be saved/loaded for the selected level.
the config page:
You can (as of version 0.23049) setup the 'Categories' within the Global configuration. First of all: this enables you to setup the default order of the columns/states for all queries. This is helpfull when you have created new custom states, that are only used for a specific type (or when you are displaying data from multiple projects, with different templates). But it also will have effect on the dependency arrows (these will now only be marked as blocking if the predecessor is within the 'proposed' or 'inProgress' category) and within a taskboard, when you collapse a workitem lane, you will get totals per category, this also is based on this configuration.
So within the following two examples, the behaviour for the state 'Test' will be different.
{
"categories": {
"proposed": [
"new"
],
"inProgress": [
"active",
"test"
],
"resolved": [
"resolved"
],
"completed": [
"closed"
]
}
}
or
{
"categories": {
"proposed": [
"new"
],
"inProgress": [
"active"
],
"resolved": [
"test",
"resolved"
],
"completed": [
"closed"
]
}
}
All,
I am adding some extra possibilities to globalize the configurations.
Kr Edward