it seems like parent/child tasks are not linked in any meaningful way. if i set the parent tasks to complete this should mean that the child tasks are complete, or in testing. etc.
is it possible to cascade some changes to sub-tasks? if for example i want to move a parent to a different fix version, now i have to make this change on every sub task.
No, they're not linked automatically, because people have different needs for their interaction
Some don't need any updates, some need data to cascade down, others need it to roll up, some just need blocks on processes ("do not allow close of parent while sub-tasks are open, but don't touch data on other issues just because you've changed something on one issue", for example). There's no way to define a rule that would work for everyone, hence there's no way to code for it.
You'll need to find or write plugins that implement your particular business logic. There's quite a few in the marketplace, but frankly, use the "script runner" plugin. You'll need to learn a bit of coding and the Jira api, but the examples provided are really good, and you'll find your coding becomes copy and tweak (and, of course, trawl "answers" for code and ideas)
Oh. OnDemand. Right.
No script runner, and most of the plugins that do this stuff are disallowed too.
You should have the "block transition unless subtasks are in status" condition for your workflows though, and "Jira misc workflows" has a few post-functions for updating parent/child issues
No, these are all features of the workflow. You use conditions to prevent people doing transitions that are unwanted (like closing parents while child issues are still open) and post-functions to update data once a user has confirmed the transition should happen.
Fields are (almost) all separate entities, they do not have anything to do with each other.
Would conditions allow all child tasks to be changed in status if the parent is changed to a particular status? E.G. if the parent is moved to a status that would effectively close it or put it on the back burner, could it be set up that the subtasks are similarly affected?
That's two different questions.
1) Conditions - absolutely not. All they do is say "can the current user perform this transition?" They are a check, they do not alter data
2) Yes, you can do this, but it should be done in a post-function or listener. Which you don't have many of in OnDemand. From memory, I don't think you've got anything that would do it, but the simple answer is try - edit a workflow, add a post-function and see what's available.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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!
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