What's the best way to map and import the following structure of project?

[Gina Preoteasa]

I have a development project with a WBS like this:

Can you please advise me what would be the best structure ?

How cand I best map, Phase , Sub stage, Phase , Activity and Task?

I thought like this:

• Phase -> Plan
• Sub stage -> Board
• Activity -> Task
• Task -> Sub-task

Would that be correct? Is there a better way?

Also, can I configure a bulk import for everything or only tasks and sub-tasks?

Thank you dearly for all your support.

Kind regards,

Gina

[Jack Brickey · Accepted solution]

Hi Gina, so you can certainly import issues (tasks) into a project using a CSV file. However, based on your thoughts I wanted to share w/ you some concepts of how Jira works.

When you import issues you map csv fields (columns) to fields in Jira issues. Nothing goes into a "board" at least not from an import perspective. You can later create and define your boards as you see fit. Within the limitations of what is offered of course.

Looking at your spreadsheet here are my comments:

By default issue types in Jira include: Epic, Story, Task, Sub-task but you can create your own issue types if desired. Most of your WBS column, I think fall into some form of issue type. For example, Stage might be a Story or even an Epic if very large. As for Phase I think it depends on the definition. For example, it might equate to a release (Fix version) or a sprint.

it is difficult to give you my final view w/o really understanding this better. You also mention "Plan" above so I'm assuming you are not on Jira Cloud Standard as it doesn't offer this concept.