Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Copying story points when cloning an issue

Hi anyone ;)

I'm trying to copy the story points from an issue when it is cloned and can't seem to be able to do it.


In clone issue into same project, same issue type

summary reads:  CLONE - {{issue.summary}}

I select Story Points in choose fields to set and set the value at 8

When the task is run I get the following error and the clone is created but does not fill the points in.

Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Story Points (customfield_10006)
Issues cloned successfully
Any pointers or help would be great thanks


2 answers

1 accepted

0 votes
Answer accepted

In our instance, it was a lot simpler. 

We just needed to add Story Points to the create issue screen and it then worked.  Seems it wasn't on the screen so couldn't fulfil the action.

Once added it works fine.

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 03, 2022

Hi Drew,

I've seen this problem before.  I think the root cause is in regards to team-managed projects having a separate, and second "Story Points" field.  This causes a lot of confusion for automation when having to then copy this field.  I suspect that the field you entered this value to, is not actually the customerfield_10006 field (which is also named Story points).

Check out this thread

A number of users have reported a similar problem, but I think we have found some workarounds here of using {{issue.story points estimate}} smart value instead here to refer to this alternative story point field.

Check out that thread and let me know if that helps.


Hey Andy, we were able to get to the bottom of it and I've posted as our answer in this thread.  Your response got us thinking and investigating it bit more and getting there so thanks!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events