Jira Portfolio functional gaps and/or limitations

Tim.Gugino May 18, 2015

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.

4 answers

3 votes
Martin Suntinger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 18, 2015

Hi Tim, 

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: 

https://jira.atlassian.com/issues?jql=project = JPO AND resolution = Unresolved ORDER BY votes DESC, priority DESC, updated DESC

1 vote
Tim.Gugino May 21, 2015

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?

Tim

1 vote
Tim.Gugino May 19, 2015

Hi Martin,

Thanks for sharing. What are the target production release dates for the JPO-10, JPO-101, requests? 

Tim

0 votes
keshav murthy May 24, 2015

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.

KEshav

Suggest an answer

Log in or Sign up to answer