Updating Task Sprint field when moving linked User Story between Sprints/Backlog

[Пономарёв Михаил]

Hello.

I was asked to configure Jira to show a tree of User Stories with multiple Tasks under each, grouped by Sprint, like this:

• Sprint 1
  
  • User Story 1
    
    • Task 1
    • Task 2
  • User Story 2
    
    • Task 3
  • ...
• Sprint 2
  
  • ...
• Backlog
  
  • User Story3
    
    • Task 4
  • ...

So I decided that any Task must be linked to it's respective User Story with Issue Link - Split From. This way I have User Stories split to Tasks.

To display the tree, I have configured a Structure that:

1. Selects User Stories with Filter synchronizer
2. Groups Tasks using Issue Links:
   
   • Links (Issue split)
   • Source of Truth: Structure
   • Structure primacy
   • Parent issue split to sub-issue
   • Sync issues in structure and all sub-issues linked from them
   • Move sub-issues with no incoming links upwards
3. Then sorts using Agile:
   
   • Agile (board Agile Board)
   • Source of Truth: Structure
   • Epics synchronized
   • Rank synchronized
   • Consecutive ranking
   • Sub-task position forced
   • Groups User Stories by Sprint using Automation

Now it displays perfect, and even when I move User Stories to change their Agile Rank in Structure, Agile Board reflects those changes.

The problem comes when i add a User Story to a Sprint in the Structure. Tasks that the User Story is split to, are not getting into the Sprint, their Sprint field remains empty.

How can I achieve that when I move a User Story into a Sprint, all the Tasks, that are linked as Split From the User Story, get into that Sprint?

Thank you!

P.S.: Don't mark my post as Spam and delete it please, like the previous time, it's a real question.

[Stepan Kholodov _ALM Works_ · Accepted solution]

Hello Mikhail,

The grouping by Sprint only works on a particular level of a structure, so when an issue with sub-issues is moved between groups, its sub-issues are not updated according to a new Sprint. It is possible to set a new Sprint for all linked issues in case of using Sub-tasks instead of Tasks or by using a script.

If you have more questions about Structure, please feel free to connact us at our Service Desk portal at support.almworks.com and we will get back to you shortly.

Best regards,
Stepan Kholodov
ALM Works

[Пономарёв Михаил]

Thank you

Already using sub-issues, works well