Cloning Epic and child Stories

Senthil V April 12, 2024

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)

Edit issue
Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Epic Name (customfield_10009)
No fields or field values to edit for issues (could be due to some field values not existing in a given project):

1 answer

1 accepted

0 votes
Answer accepted
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 12, 2024

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

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 12, 2024
Like # people like this
Senthil V April 15, 2024

Thank you @Stephen Wright _Elabor8_ and @Trudy Claspill . I replaced Epic Name and Epic Lin with Summary & Parent field respectively. It worked out successfully without any warning errors.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events