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:
Again, what are the target production release dates for the JPO-10, JPO-101, requests? Are these issues on a backlog that will be release to production within the next 30 days, and if not when?
are there any limitations in trial version v/s licensed version? I am expecting basic things like importing current spring plan to portfolio but there is no option.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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