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
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
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.