An alternative is to add epics and tasks. An epic is some big piece of functionality the business wants that is delivered via multiple smaller stories. Epics, by definition, break the rule that stories must be small, but they have the most business benefit. Tasks are smaller work items that build a story. They usually can be accomplished in a
You can't move standard issue (bug) and other standard issue type task. You want to move this , you can convert issue type to sub-task using convert to sub-task option. With this you can mention task ID as parent for the sub-task. Thank you. Yes, this I know, I just guess if it possible to move the issue as a Bug not converting it into a sub-task. Select the search field in the navigation bar and select View all issues. Click the Project filter, and select the project you want to migrate from. (If you're looking at the Advanced mode, you'll need to select Basic) In the top-right corner, select more () > Bulk change all. In such a case the Product Owner had to create a new epic, enter necessary details and move backlog items to it. For such a situation, we added a new command Convert backlog item to epic. Select any backlog item card and choose click the icon in the side view. The backlog item details will be transferred to the new backlog. Khadhar Mohaideen Oct 08, 2018. I have a requirement where we want to introduce Features as an issue type with the hierarchy of Epic --> Feature ---> Story ---> Sub-tasks., where we should be able to link Features as children of Epic and Stories as children of Features (with a filed similar to "Epic Link", such as "Feature Link" which links The important points are the epic needs to be in the csv before the stories to be linked to it. Then you can use the Epic Name in a column for the stories which is then mapped to the Epic Link field. Hope this helps you import. Another option if you always have the same set of stories every time you create an epic it may be worth investing some ARvUr.