Request for Guidance on Reassigning Custom Issue Types

Alexander Bassoukas-Remscheid

Hi Team,

In our project, we have identified the need to track our custom issue type more effectively. This requires transferring over 300 issues from the “Epic” level to the “User Story” level.

Questions:

1. What do we need to consider when reassigning these issues?
2. What impact will this have on the child issue types of the requirements?
3. Are there any other ways to make the “requirements” plannable on a sprint board/backlog?

Thank you for your assistance.

Best regards,
Alex

Dick

Hi @Alexander Bassoukas-Remscheid Welcome to the Atlassian Community.

 

1. Thing you should consider include: 

• You're going to loose the field "Epic Name" (it is not available for the user story issuetype)
• Child issues of the epic should become sub-tasks under the correct user story

2. Impact on child issues:

• The epic link is going to be emptied. 
• The parent link field needs to be set to the newly created user story
• No other problems 

3. Also Epics have requirements.
    These requirements are met by finishing the user stories that are attached to it. Often people have two boards: one board containing the epics (read: longer term goals) accompanied with a second board for the daily operations (the user story board).

 

It is advisable to use a couple of non-used fields (or even temporarily make a couple of custom fields) to store the content of the original epic key and epic-link values. This allows you to roll back your change.

Test the change sequence of bulk operations on a small test project first. This is a major undertaking when performing this on a live project.

 

Hope you get the move on

Dick

By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well