@Jaime Anderson, Yes I would make your website a project. Yes I would use Component for the various areas especially if you have different leads for the components so that you can assign to them. I realize it can be overwhelming to get started but you can always change things as you go forward. Obviously the more you get 'right' out of the gate the better simply because you won't have to retrain.
Things to think about that drives setting up a project:
- Who are the players and do you want to auto-assign issues to them based upon some variable, e.g. Component
- What Issue Types do you need/want (Task, Story, Epic, Sub-tasks, Bug, Enhancement, etc)
- What workflow do you want. My advise, from learning the hard way, is to keep it as simple as possible, e.g. To Do -> In Progress -> Done. But that might be too simple for your needs.
- Permissions - do you need to restrict access
- Notifications - who needs to be notified and when. My advice is to limit notifications to what is actionable otherwise your team will be inundated by notification emails and stop looking.
Bottomline - don't over engineer up front. Tweak once you are sure a change is needed.
Final Advice - Use the Community as it is a great resource w/ lots of excellent users w/ experience.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.