A broad question about sub-tasks

Hi there,

This may be too broad to answer but I guess I am seeking opinion.

I am working on workflows which revolve around the creation of an article, from commissioning, throught writing, to proofing and publication on a website at which point the issue is closed. This element of the workflow remains clear to me.

I do have a requirement within these workflows however for the document to go to translation - this is essentially a branching off of the workflow which would run in addition to the above order. Would logic and experience suggest that translation is a sub-task? Is there a way that the issue cannot be closed until that sub-task (translation) is completed?

Thanks for any insight.

Best wishes

Paul

1 answer

1 accepted

Accepted Answer
0 votes

Hi Paul,

Yes you can block the parent issue transition using subtask blocking condition. Take a look at

https://confluence.atlassian.com/display/JIRA040/Configuring+Workflow#ConfiguringWorkflow-conditions

If all translation tasks are related to the article (main issue), then there is no reason why you should not create them as subtasks.

Cheers

Bhushan

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

463 views 7 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you