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

Using the Create button under delivery doesn't copy a description to the new card

Since we can't move or clone anything, and we have to create a copy for delivery, I expected my idea description to copy to the card I created on a software project, but it doesn't. Only the summary appears to copy to the new issue and I have to copy/paste and re-link everything to the new issue that I already had on the idea so the developer has it.


Will it always work this way?  It's a lot of rework if someone spends time on their idea. 

2 answers

1 vote
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 19, 2022

Hi @sharon.prajzner

Currently the idea is accessible via an issue link in the delivery issue in Jira Software. We plan to show more information there (for example the description of the idea, and a selection of fields) - as currently just having an issue link is a bit "dry". 

However we do see the 2 as having a different purpose: the idea is where you collect insights and decide why you want to prioritize something (the problem it's solving, the solutions explored, how you plan to measure success, etc.) while the delivery issue/epic should focus on how you plan to deliver it (break down into tasks/releases/etc.)

I would ask "why" are you making a full copy for the Delivery aspect?  The link will always exist and hold all the background.  The Delivery piece will be an epic which doesn't always need a ton of info and stories will end up being broken down anyway.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events