Hi Team,
I want to be able to setup a template Epic -> Stories -> Sub-tasks and then have a manual rule that clones this 'tree' of issues...
I've managed to get part of the way there, in fact the Epic is just created on the fly, then I gather up a set of Story items tagged with a 'template' component and link them to the Epic, but, as the branching rule condition cannot be nested I can't see a way of cloning the story items and their sub-tasks...
I could theoretically allow the rule to call another rule, but that seems a little dangerous...
Any advice on this?
Thanks,
Simon
Hi Simon,
For this I think you are better off doing this 2 rules:
First rule should be fairly simple.
{
"properties": [ { "key": "orig-story", "value": "{{issue.key}}" }
]
}
The second rule:
This is a fairly complicated rule but we have had talks internally about Syncing/Cloning a hierarchy. This would make it trivial.
Cheers,
Nick Menere [Code Barrel]
Automation for Jira
Ah, awesome, I couldn't quite understand how properties worked, that's great, many thanks,
Simon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.