Hello @Trudy Claspill - In one of your post with this automation rule for cloning Epic hierarchy with stories, I am getting an error message but the clone seems to be successful.
Can you please confirm if this a valid error?
Your Automation Rule:
TRIGGER: Issues Linked
- Link Type: Cloners
CONDITION: Issue field condition
- Field: Issue Type
- Condition: equals
- Value: Epic
BRANCH RULE/RELATED ISSUES: JQL
- JQL: "Epic Link" = {{destinationIssue}} order by key asc
ACTION: Clone Issue
- Project: Same Project
- Issue Type: Same issue type
- Fields to set:
- Summary: {{issue.summary}}
- Epic Link: {{triggerIssue}}
ACTION: Delete Issue Links
- Link Type: is cloned by
ACTION: Edit issue
- Fields to edit:
- Epic Name: {{issue.key}}
Error Message on Edit Issue Action (last one)
Hi @Senthil V
Epic Name is (or is becoming) a deprecated field; Epics use their Summary now for the Epic Name functionality.
Is there a reason you're trying to set this field?
I'd also change Epic Link > Parent, as Epic Link is also going to be deprecated.
Ste
FYI - the other post mentioned by @Senthil V is
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Ste Wright and @Trudy Claspill . I replaced Epic Name and Epic Lin with Summary & Parent field respectively. It worked out successfully without any warning errors.
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.