Hello,
I want to create an automation.
When I create an interface task from an Epic, I would like to copy values from the Epic (Account, Customer, Account owner, Epic name) to the interface task.
The fields are noted in the epic.
What is surprising is "Can't find issue" :
Yet I used the specific icon :
Could you help me ?
Best regards,
Estelle Decanis
This may be a timing problem; when the issue created trigger fires it is possible all of the data is not yet available for use. For example, the epic link value.
The way to check that, is immediately after your rule trigger add a Re-fetch action. This will slow down the rule and reload the data before proceeding.
Kind regards,
Bill
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.
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.
Hi Estelle,
Try adding a Branch before you do the Edit issue action.
The Branch should be Epic (Parent). Then place the Edit issue action under the branch.
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.
Can you share a screenshot of your current rule?
And what doesn't work? Do you get an error? What doees the audit log say?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I went back to basics and it worked.
So that tells me there is something wrong wtih a screen or a field or something like that.
Is the Epic on the same project as the task you are creating?
Is the Epic Link populated at the time of creation of the task?
Are the fields being copied on both the screens for the Epic and the task (Create Screen)?
Do the fields have a context that includes the Issue Type of the task being created?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You said "The Branch should be Epic (Parent)" and it doesn't work. In your test I don't see the Epic branch.
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.
Hello @Estelle Decanis
Are the issues in a Company Managed project or a Team Managed project? If in a Team Managed project try the "copy from Parent" option instead of "copy from "Epic".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Trudy Claspill
The issues are in a Company Managed project. I had tried "copy from parent" but got the same result
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I suggested that only for a Team Managed project, as Team Managed project issues track their parent Epic in the Parent field rather than the Epic Link field.
I haven't tried such an automation rule before, but I thought it might be looking for the Epic via info in the Epic Link field when you use "copy from Epic", and that might not work for Team Managed project issues.
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.