hierarchy is given below
EPIC->Feature->User Story->Task/Testcase/BUG
i am facing issue while importing it's importing individual.
Jira only supports Issue -> Sub-task. (Note that I'm using Jira-speak here - you can have many different names for the issue and sub-task types. Almost all of us have an issue type called "story" at the issue level. I'm talking about layers or levels here, not specific named types)
Jira Software enables Epic -> Issue -> Sub-task
You can then add Advanced Roadmaps, Structure, Jira Align, Big-Picture and so-on to enable more layers, but you'll need to think about how to map them all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, you can import fields from Redmine, as well as attachments.
There's no import of users directly, but you can tell Jira to create missing users from the issue data. If, for example, you don't have Bob as a user in Jira, but your import data has Bob as a reporter, assignee, authoriser, participant etc, Jira can create an account for Bob.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Hema
I would like to add only a few words about BigPicture. As @Nic Brough -Adaptavist- mentioned in BigPicture/BigGantt, you can automatically create a no-limited number of WBS levels. Task Structure can be created based on both build-in task attributes (e.g., Epic link, Component, Version, Sprint) as well as links.
Even though stories and tasks are on the same level in Jira, in BigPicture, you can create a hierarchy similar to the one between epic-story.
Let me know if you have further questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.