Can we create the dependency between the sub-tasks

[M Vijay Kumar]

Hi All,

we have parent tasks and sub-tasks that have been loaded into JIRA using ceptha plug-in. As of now we have parent tasks and its associated sub tasks in Jira.

I would like to check is there a way we can control the sub-tasks. For sample, if we have Parent Task A and the associated sub-tasks are Sub-task A, Sub-Task B and Sub-Task C.

The requirement is Sub-Task B cannot be started until Sub-task A has completed and similarly Sub-Task C cannot be started until Sub-task B is completed. In simple words, under a single parent task only one sub-task should be in progress. Is there a way to do this. Any information provided will be useful.

Thanks,

Vijay

[Nicolas Bourdages]

That's a job for Issue Links.

If you want Subtask A to be completed before Subtask B, you need to set an issue link so that Subtask A blocks Subatask B.

After that, you have to educate your people to pay attention to issue links and these kinds of dependencies, so they only start working on subtasks that aren't blocked. It takes a little while and people will make mistakes, but since you're using Cloud, you can't use the more advanced workflow validators plugins like ScriptRunner.

[M Vijay Kumar]

Hi Nicolas,

Thank you for your response. I just wanted to confirm whether blocking will allow to start the progress of the Sub-task that has been blocked by other sub-task in Jira.

For example. if Sub-Task A blocks Sub-Task B, it typically means Sub-task B has to start after Sub-task A, but I could see that Sub-Task B can also be started/edited although the Sub-task A is in progress.

If I am not wrong, once the linking is done, we need to educate the people saying that blocking doesn't have tight control on the dependency of the sub-tasks but they should be educated in a way to see the 'Link' of the sub-task and proceed further.

Thanks,

Vijay

[Shee Covarrubias]

What portion of the ScriptRunner is used to have the dependencies systematically locked?

[Nic Brough -Adaptavist-]

You can't "lock" issues.  So there's nothing ScriptRunner can do.