You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Under Administration>Issues select "Issue Type Screen Schemes" and find the scheme associated with the project you are working in then click on configure. Does the Issue type Story have the same Screen Scheme as Epic? If so, then you should be able to just edit the issue type field in the issue (assuming you have permission). If the schemes are different then you can try using move.
In the issue there should be a "More" button. Click on the button and below "Convert to Sub-task" should be an option to "Move". You should be able to move the issue to story and choose what to do with fields that are present/required in one scheme and not the other.
Sadly converting an Epic incl Child Tasks to a Story with Sub-Tasks does not work as during the move operation you need to select the parent issue for the Sub-Tasks, which must be a Story and at this step of the conversion the parent is still an Epic. So it is impossible to directly convert an Epic to a Story if it contains Child Tasks.
In addition a warning: If you convert an Epic with Child Tasks to a Story and set "Task" for the Child Tasks, their parent is removed without (!) warning (as a Story can't have Tasks as Child). So you finally would get a Story and all Child Tasks are independent Tasks on their own! And you can't rollback this change!
Now you can re-use the dummy Story for other Epics, which needed to be converted, too, but you have to do this for each Epic separately.