Card layout not refreshing

[Idan Tene]

Hey!

I've spent some time creating automation rules that reflect a card's progress using subtasks using time estimates.

The Kanban board does show subtasks, and instead it shows the sum of progress. The automation rules work nicely, but the card layout does not update automatically.

I have to "trigger" the update by either moving the story to a different status, or by adding/removing a field from the card layout.

Is this a known issue? Is there a way to force-refresh the card layout?

EDIT: An additional question, tangent to the topic, is it possible to reset the timeSpent field? I noticed one can only add to it.

[Idan Tene]

I've found my solution meanwhile, though I believe this is not optimal.

Instead of updating the subtasks' estimates and using the sum-progress field, which apparently does not cause the aforementioned reindexing/refreshing, I instead update the parent story's estimates.

This directly changes the story's fields, and hence (probably) causes a refresh.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Kanban does not have estimates, so that's why you have to build an automation (you're not doing Kanban if you're putting estimates on cards)

What is the trigger for your automation, and what is it set up to change (value on a different issue, the current issue, an epic, etc)?  

[Idan Tene]

Hey @Nic Brough -Adaptavist-,

I'm aware Kanban does not have estimates, I'm leveraging the built-in time estimates (original, remaining, and time spent) to solve this issue, which seemed to get no love nor care.

Basically, we'd like a story's subtasks-based progress bar to show up on the Kanban board. That feature does not work. So I've resorted to leveraging the worklog, with the following automations (not perfect, but it works well enough):

1. When creating a new subtask, add an original and remaining estimate of 1m.
2. When transitioning a subtask to done, add 1m to the time spent on the task.
3. When transitioning a subtask from done to something else, add 1m to the remaining estimate.

Then, the Kanban board's card layout shows the sum-of-progress as a field, as well as the subtasks field. It works well, hurray!

However, the board does not update automatically once a subtask is updated. I have to e.g. move the entire story to a different status, or remove/add a field in the card layout, to trigger this refresh.

[Nic Brough -Adaptavist-]

Does it update when you refresh the browser tab?

[Idan Tene]

It does not. It really feels like some trigger is required for the card layout to update.

[Nic Brough -Adaptavist-]

If a refresh is not updating the view of the content of a field, then the most likely explanation is that your code is not actually changing the field, or if it is, it is not causing the issue to be re-indexed.

[Idan Tene]

It definitely update the sub-tasks' fields, and so the sum-of-progress is also definitely updated. The parent story is not directly modified otherwise.

I suspect it is not causing the re-indexing then. Is there any way to trigger that?

[Nic Brough -Adaptavist-]

Automations should be indexing issues automatically, so we'll probably need to see exactly what automations you have created, including triggers, and exactly what they try to update.

[Idan Tene]

Alright then :)

Here are the automations and the card layout in the board.

[Idan Tene]

To further illustrate the flow I'm encountering:

1. I create a new story.
2. In that story, I create a new subtask.
   1. The subtask automation runs, and sets the original estimate and remaining estimate to 1.
3. The ticket in the kanban does not show the progress, nor the subtask in the sub-tasks field.
4. I can repeat (2) and add another task - still no visual update happens.
5. I can also transition any of the subtasks to done, and the automation works perfectly, but still no visual update happens in the board.
   The story ticket shows None for both fields.
6. I transition the story to any other status - and only then it updates those fields visually.