Im Badly looking into solution for my project.
Example: i have different team for everything like Design, UI, Coding and Testing
Each team has different set of activity to perform to complete one modules. Note: we have around 50 modules as part of single project.
I'm not sure what would be best way to use it in JIRA.
Note: using Sprint as development methodology for our project.
Can any body explain: how epic , user stories will be used and what to mapped to it... please help
Hi @fastersaec ,
Welcome to the world of Jira and its new user feeling of the weird dichotomy of "it doesn't do much out of the box" and that feeling of "this thing is huge" lurking in the background. That said, from your question, you are already heading a good direction to keep each of your different teams in their own projects so their processes and work can work in their own way without impacting other teams.
As such, I'll start with your immediate discrete question about epics, stories, etc., and then some general things to help you on your way (or at least things to start looking for as you start this journey).
In Jira, the base element of a "thing" is the issue. What you cited are a set of different issue types and, with that , different categories of issue types. In brief, and as delivered out of the box, Jira has as an issue hierarchy:
Of these issue types/categories, the one that is "locked down" is the "Epic" with it being (out of the box) the only issue type that can exist at that level of the hierarchy. However, a "Story" is merely a pre-packaged issue type in the "regular issue" category and "Subtask" is a pre-packaged issue type in the "subtask" category. As such, you can create new issue types called whatever is meaningful in your environment in the regular and subtask categories and have them respect the above hierarchy.
With that stated, now, there is the rest of this giant thing to look at and, while that is rather larger than a breadbox, I'll give you a few places to start looking as you get started with this.
With that bit of drinking from a firehose now stated, and remembering that you will eventually fall into the issue security, etc realm, that should get you started on places to start working with this thing. I highly recommend that you spin a test instance and a methodology to migrate your production data to test so you can try things there with little consequence. Any of the well written Atlassian pages or very good examples in the Community here of how to migrate a Jira instance to a new server (which is what making a test instance really is) will serve you well.
With that... good luck and as you have more questions which will become more specific once you get past the "what the heck do I do with this thing now" feeling all of us went through, do reach out here and/or look here for potential answers. There are a lot of us that, while some might suggest we question our life choices that got us here, enjoy working with Jira and are happy to help.
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