We recently purchased Jira OnDemand and are converting from ClearQuest.We are considering changing the way we had projects laid out and were curious if there were any best practices as to how a project should be structured.
We are also considering implementing greenhopper. what influences does that have on a project structure? Is it an entire project represented on a greenhopper board or can it be a subset of a project?
Hi Michael, 'best practices' is something difficult to say. As far as I know Jira's project can be structured in such a lot of ways.
In my case I created one project category per client, and inside that category I have all projects for the client, such as New Developments, Bugs Support, Security Implementation and others.
And I almost have one workflow per issuetype per client. For example, New Feature has clientx_workflow and clienty_workflow.
I have issuetypes scheme per type of project, for example, every client has a project 'Bugs Support' and there's an issue scheme with 4 issutypes for all 'Bugs support' projects.
And I continue like that... There are a lot ways on how to configure everything, it's only important to discover how is better for you company.
Hope this helps.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs