Current situation
I am using this new feature to have columns for iterations described here #39
Although I would like to use the macro @CurrentIteration to get dynamically always the current sprint and next sprint per column.
For the moment this is hardcoded with the Sprint name.
Expected bahavior
In the JSON-document I could write the macro to dynamically get the current sprint
with for example: "name":"<Name Project>\\@CurrentIteration"
I doubt this is already supported but this would definitely be a nice addition to have!
For me, three options would suffice to fulfil the outcome requirements (in case one of the options isnt suitable for implementation):
apply the above advanced configuration - column configuration containing the "@CurrentIteration" or "@CurrentIteration+1" macros; the extension would 'translate' this into the applicable current iteration when rendering the Taskboard.
Instead of configuring individual columns, provide a general "Iteration Path Configuration" option, which then either dynamically displays/renders all Iterations included in the query results,
or (if all iterations as per result wouldnt work) which displays/renders a predefined set of Iteration columns (such as current and next iteration).
Hi!
Current situation I am using this new feature to have columns for iterations described here #39 Although I would like to use the macro @CurrentIteration to get dynamically always the current sprint and next sprint per column. For the moment this is hardcoded with the Sprint name.
Expected bahavior In the JSON-document I could write the macro to dynamically get the current sprint with for example:
"name":"<Name Project>\\@CurrentIteration"
I doubt this is already supported but this would definitely be a nice addition to have!