hi community,
my dilemma is an automation rule which I couldn't get running.
We want to copy a value from a custom field (10134) of issuetype X in project A to its linked issues of issuetype epic in project B. The issues are linked with type "relates". Both issuetypes are using the custom field (10134). The rule shall perform once a day.
I'm struggling with the configuration.
You need to use a branch in your rule based on linked issues of the type relates to.
Branch after your condition.
Example:
hi @Marc - Devoteam,
thanks for quick answer. Similiar configurations I've tried already but as you can see in the second screenshot, the audit log tells me that there is no issue found.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is the config of the scheduled trigger, is there a JQL clause stated?
If so remove it, as the JQL is in your clause.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your last answer brought me on the right way.
I used "issuetype = epic" for the trigger but as you wrote correctly it was redundant. Instead I changed the trigger's jql request to "project = PN AND issuetype = Projekt AND "ZEP-Projekt (Link)" != Empty". "type = epic" is now used just once in branch's condition (key = ... was only for a test run).
Hopefully, it does now what i expect.
One additional question: Soon, I'd like to add more issue fields but I only wanna copy values from issues where the fields aren't empty. How can I request that for several fields where at least one of it is not empty? And would the rule also copy empty fields to a maybe non-empty field? That would be counterproductive.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then you would need IF/ELSE clause and then branch in the clause.
Yes if you copy fields on the eit and the field is empty, the existing value will be overwritten.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.