Hey JIRA experts!
I’m trying to streamline our workflow and need some help with automating subtask movements. Here’s what I’m hoping to achieve:
-
When all subtasks under a story are finished, can the story automatically move to ‘Done’?
-
If I drag a story from one column to another (like ‘Idea’ to ‘Backlog’), is there a way to make all its subtasks follow along?
Our board setup is pretty straightforward:
- PO board: Shows only stories, uses epics as swimlanes
- Dev board: Displays subtasks, uses stories as swimlanes
The PO can’t see subtasks, and devs can’t move stories to ‘Done’ - they only handle subtasks.
Has anyone figured out how to make this work? Any tips or tricks would be super helpful! Thanks in advance!
I’ve implemented something similar in our JIRA setup. For your first question, JIRA’s built-in automation rules can handle transitioning a story to ‘Done’ when all its subtasks are resolved. You would set up a trigger that checks the status of all child tasks and then automatically transitions the parent story.
For moving subtasks along with the story, it’s more complex because this isn’t supported out of the box. Our solution involved using JIRA’s REST API along with a custom script that monitored the parent story’s movement and updated subtasks accordingly. This approach requires careful testing to avoid side effects in production.
As someone who’s been in the JIRA trenches for years, I can tell you that automating these workflows is definitely possible, but it requires some finesse. For the first part, JIRA’s built-in automation rules are your friend. You can set up a rule that triggers when all subtasks are completed, automatically moving the parent story to ‘Done’. It’s straightforward to configure and works like a charm.
Now, for moving subtasks with the story, that’s where things get trickier. JIRA doesn’t offer this out of the box, so you’ll need to get creative. In my experience, the most reliable solution involves using a combination of JIRA’s REST API and a custom script. We implemented this using a server-side script that listens for story movements and updates the subtasks accordingly. It took some trial and error to get right, but it’s been a game-changer for our workflow efficiency.
Just a word of caution: thoroughly test any custom solutions in a sandbox environment before deploying to production. You don’t want to accidentally mess up your entire project structure!
hi, i’ve seen this before. jira automations can handl the story move when all subtasks are complete.
for moving subtasks with the story, you probably need a plugin like scriptrunner or custom scripting.