We've been evaluating JIRA for our purposes for quite some time now. However, we haven't managed to figure out the correct (or standard) way to set up our JIRA hierarchy properly (Projects / Components etc) so it'll properly capture our needs and use-cases.
A top-level overview of our "Actors" would be:
1. Clients (external or internal)
2. Products - For example iPad-app, iPhone-app, Android phone-app, PC-app etc.
3. Components - Different functionality groups - For example Social, Main-Menu, Gallery etc.
3.1. Components customizations - Specific customizations of a component for a specific client
The standard flow is that a release to a Client is a subset of our Products and within these Products a Subset of the Components and their respective customizations. Obviously we'd like to open issues where they're relevant, so if there's an issue in the core functionality of a component, it should appear in all Products/Clients.
I'd be glad to hear ideas or prior experience with this kind of work flow,
Label semantics very loosely couple issues with components/clients and act (as I see it) as search terms rather than logical grouping of issues/versions etc.
In this regard I could just use some other "free-association" tool like asana and have less hassele setting up etc. I'd like to use JIRA's powerful feature-set and not as kind of "google for issues".
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot