I am charged with two initiatives that will probably require me to change our JIRA config to accommodate.
I would be interested in hearing how others who have experienced the above, or theoretical, would design their JIRA instance. For #1, I was leaning towards creating a project named Roadmap, put all the Roadmap items in it and use that as a central backlog, moving the tickets to the appropriate team when development begins. Thoughts??
For #2, this feels more daunting and could be susceptible to over-configuring. I do need to get more clarity from the CTO on what the actual team structure will be. We are online retail. What I am worried is that if you break our feature set into functionally atomic pieces, we could have 20-25 areas and thus 20-25 different projects (Home page, promotional logic and functionality, Product List pages, Product Detail pages, Profile, Checkout, Product array and synchronization, and on and on). We are not a large company and potentially having 1-2 projects for each of our Eng headcount seems ludicrous. :)
My gut is to go ahead with my proposal for #1, and not change for #2 until we find our config to be broken, but have a couple of models ready to go in case we need to make changes rapidly.
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