how should I start to define issues in Jira? what is the first step? I want to know what is the most effective way to categorize issues? is it ok to start with epics or is there another way?
I will be thankful if any one has any related experience to guide me please?
First create project, and then few component in that project.
Once this is done, create Epic and then Story and then Task and Sub-Task in Jira.
Project --> Component --> Epic -> Story --> Task --> Sub-Task
This is what I am following for more than 4-5 years.
@masha yoosefinejadComponents are sub section of project, they are not issue types.
You can look at this knowledge base article by Atlassian - https://confluence.atlassian.com/adminjiraserver/managing-components-938847187.html
I would suggest the Atlassian product guides are a good place to start - you can view these by clicking here
It's important to structure your work in the best way for you. The good thing is it's really difficult to do the wrong thing in Jira as it is designed to be flexible.
A few pointers which I find help our teams:
I find deciding the basics can be a great way to start. Epics and stories - if you're using these already, you could create your stories first and link them to epics later - or create your epics and then add stories into them. Either way is going to work.
I'd advise reading the guide I linked to - some great information for starting your Jira journey :)
Hi, thanks a lot for your complete answer and advice.
Could you please guide me more? Shall I create TASK for every story? and link them to the story or epic?
In my organization every story is related to a specific team.. For example a feature that the customer wants can be dived to 10 stories that each of them is related to a team. Teams members do their task and close them. In each sprint we can monitor which user story is not completed and why?
Do you think is it a good pattern or not?
Your teams need to decide the best way for them to work - but here's some advice on how I break down work:
^ We also have Features above the Epics - which are larger, releasable parts of the product. This is added as part of the Portfolio add-on.
I guess the difference is we use stories at a single user level - rather than Sub-tasks. Also looking at DPK's model we don't have Task between Story and Sub-task - we use Tasks for Technical BAU (so it's the same level as Story). We find this works better with the standard Jira hierarchy.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events