nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can you create a way for one task to create the start of another?

Timothy Brainard

I'm looking to try and sequence the order of tasks so that a group of tasks aren't released all at the same time. For example, 1. order new part 2. inspect new part upon arrival 3. Install the new part.

What I'm wanting is when we release this process that the number 1 task would go out and once it was signed off as complete it would send the number 2 task out and so on. Currently all tasks are send out in a group and it leads to some confusion.

Thank You

Accepted answers

Mikael Sandberg

You could accomplish this with an app. There are a couple of them on the Marketplace. We use ScriptRunner to do similar, depending on where an issue is in the workflow, a new task will be created and linked to the parent one. Automation for Jira and Power script for Jira are two other apps can do this too.