We are considering procuring the JIRA Portfolio add-on and want to make sure we consider all the issues prior to making the buying decision. What are some of the primary functional gaps and/or limitations of the tool? I realize to tool is early in its life and there are limitations of the tool. Any opinions would be appreciated.
I'm the product manager for JIRA Portfolio at Atlassian. From Atlassian side, whilst the tool is seeing great adoption already and provides a lot of value we also want to be open about areas to improve - as you noted, the product is still early in its life. Looking at customer-reported suggestions and top-voted issues on jira.atlassian.com for the JIRA Portfolio project will give you a good overview. Definitely the biggest hot spot is to provide a more seamless workflow in association with JIRA Agile, both in handover from planning to execution, and in terms of updates back to the plan. You can find these suggestions here:
...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....
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