8,712
Customers have installed this app in at least 8,712 active instances.
8,712
Customers have installed this app in at least 8,712 active instances.
    by Atlassianfor JIRA Cloud, JIRA Server 6.3 - 7.4.2 and more versions
    Versions available for JIRA Server 6.0 - 6.2.7
    Supported
    Atlassian supports this app.

    Get support

    Supported
    Atlassian supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.

    The agile portfolio management tool, built for JIRA

    The agile portfolio management tool, built for JIRA

    Agile roadmap planning

    Team and project visibility

    Seamless JIRA integration

    Create a real-time agile roadmap and forecast release dates.

    * Compare estimates and release dates

    * Manage team availability and skill sets

    * Create multiple "what-if" scenario plans

    Gain visibility across multiple teams and projects to keep everyone on the same page.

    * Create hierarchies and dependencies

    * Track business goals and resources

    * Easily share or embed reports

    Instantly create a plan from your data in JIRA and it'll always be up to date.

    * Get a plan in less than a 1 min.

    * Connect multiple JIRA boards and projects

    * Play in a sand-box or change everything in real-time

    Agile roadmap planning

    Team and project visibility

    Seamless JIRA integration

    Create a real-time agile roadmap and forecast release dates.

    * Compare estimates and release dates

    * Manage team availability and skill sets

    * Create multiple "what-if" scenario plans

    Gain visibility across multiple teams and projects to keep everyone on the same page.

    * Create hierarchies and dependencies

    * Track business goals and resources

    * Easily share or embed reports

    Instantly create a plan from your data in JIRA and it'll always be up to date.

    * Get a plan in less than a 1 min.

    * Connect multiple JIRA boards and projects

    * Play in a sand-box or change everything in real-time

    More details

    Made by Atlassian

    Major Features

    • Seamless integration with JIRA
    • Plan
      • Schedule dependencies
      • Plan with both story points and time-based estimates
      • Use Portfolio for JIRA custom fields in JIRA
      • NEW: Baseline original estimates and target dates
      • NEW: Create multiple "what-if" scenario plans
    • Scope
      • Track progress and status
      • Re-prioritize work items
      • Assign issues to sprints
    • Team
      • Add skills to team members
      • Configure team member availability
      • Manage shared teams
    • Releases
      • Create project-specific or cross-project releases
      • Configure release dates
      • Track if you'll meet your release date
    • Reports
      • Export reports to CSV
      • Share reports with link

    Sign up for a 30 min demo with live Q&A with Atlassian Product Advocates.

    Check out how Rosetta Stone uses Portfolio for JIRA.

    More details

    Made by Atlassian

    Major Features

    • Seamless integration with JIRA
    • Plan
      • Schedule dependencies
      • Plan with both story points and time-based estimates
      • Use Portfolio for JIRA custom fields in JIRA
      • NEW: Baseline original estimates and target dates
      • NEW: Create multiple "what-if" scenario plans
    • Scope
      • Track progress and status
      • Re-prioritize work items
      • Assign issues to sprints
    • Team
      • Add skills to team members
      • Configure team member availability
      • Manage shared teams
    • Releases
      • Create project-specific or cross-project releases
      • Configure release dates
      • Track if you'll meet your release date
    • Reports
      • Export reports to CSV
      • Share reports with link

    Sign up for a 30 min demo with live Q&A with Atlassian Product Advocates.

    Check out how Rosetta Stone uses Portfolio for JIRA.

    User reviews

    (153)
    Sign in to write a review
    by Richard Whitehead on 2017-08-07
    I found this very confusing to use, possibly because we are using the Software Development Issue Scheme, not an agile scheme. It was very confusing what was a task and subtask. Initially it scheduled everything at once, even though people were assigned to individual tasks, it ignored this. I had to assign each task to a person again in the chart. The “Gantt like chart” is not a Gantt chart, and I found it confusing because each row could contain multiple tasks, for different people. The Gantt chart is industry standard for good reason, it tells you what you want to know; if some developer thought they could improve on it, they were wrong.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Hi Richard,

    Thank you for providing your feedback on Portfolio for JIRA. We'd be more than happy to provide any support necessary to troubleshoot your Portfolio plan - please don't hesitate to reach out directly: bdavies@atlassian.com. Looking forward to speaking with you.

    All the best,

    Bree

    by javad darabi on 2017-07-22
    Hi it's really amazing and useful add on but I have problem why when I add an issue to my project It won't add to my portfolio? is it usual ?
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Hi Javad,

    Please check your plan's issue sources. You might have a filter or a board as the plan's source which might filter out some issues. If that is not the case, please contact me at rfine@atlassian.com I'll be happy to assist further.

    The Portfolio for JIRA team

    by jerry.bracke on 2017-07-12
    I was one of the early JIRA Portfolio adopters and in retrospect it was one of the worst purchases I have ever done in my entire life, I'm not exaggerating. Years of hoping this product would come to mature and telling myself "wait, it's just a phase", I have to come to the conclusion this tool will never come to it's right. Although the idea behind the tool is good, the execution of it is appalling. In use it feels rigid, limited and with zero regard to the end-user. The usability is disastrous. Just try to move the order of the columns in the overview; it is impossible. Just try to navigate to an issue, it takes you a few clicks (too many) Such simple, simple features and enhancements. One of the fallacies of the product management of this tooling is they keep on adding new big features to this product, but completely disregarding getting the basic functioning in order. I'm a big fan of Atlassian and JIRA, but my thumbs down for this. one. I'm so sorry. Wish we could get a refund for all those wasted years never ever being able to use this tool.
    8 out of 8 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Hi Jerry, I'm very sorry to hear this. We are committed to improving the experience of Portfolio - it is a major focus for us now and into the immediate future. I'd be more than happy to discuss your frustrations with you in more detail and offer any support necessary for you, please feel free to contact me directly - bdavies@atlassian.com if you'd like to talk further. Kind Regards, Bree | Portfolio for JIRA PM

    by Virginia Knight on 2017-06-29
    My Product Owners absolutely HATE using this product, and many of them have resorted to using spreadsheets and PowerPoint to communicate progress rather than fight with this tool. On this basis alone, I would give it less than 1 star. However, it does technically do all the things that it says it does, and as far as I can tell, there is no other plugin on the Marketplace that does these things, hence the 2 stars. The interface is clunky, and I find it not as pretty or polished as other tools. I can deal with that especially if the tool is relatively easy to use once you figure out where things are. But it's not. Atlassian mentions below that there is a "powerful" scheduling algorithm that needs to be well-understood to maximize the effectiveness of the tool. This understanding is CRUCIAL. Let me say it again. CRUCIAL. Otherwise, you will spend hours with each plan trying to understand why the changes you made took no effect. For example, you can set a story to start no earlier than August 1, but if its assigned to a release that can start on July 1, your setting is ignored, your story will start on July 1, and you get no helpful message to explain why. There are a number of non-intuitive things that happen like this. I wrote up a 5 page FAQ for my users explaining all of the things that may go wrong and how to fix them in their plans. For a $6000 app, I should NOT have to do that. Atlassian, in case you're listening, here's my advice to you: (1) Charge less for this thing in its current iteration, or make it awesome enough that it warrants the price. Because right now, it's not, and it doesn't. (2) Your scheduling algorithm might be "powerful", but it's wrong. In the case mentioned above, when would it ever be correct for a story to ignore its earliest start date just because the start date of a release occurs before it? Doesn't seem likely. (3) Even if you disagree with my assertion that the scheduling algorithm is wrong, at least pop more warnings about why user specified values are being ignored. (4) Please do something with the UI. For example, seeing the Gantt-like chart is an eye test that most of us fail. Figuring out how to include additional items in a plan took far longer than it should have. I could also make piles of suggestions for how to make working with the product a more delightful experience, but I'd settle for it not to be a bad experience. (5) It seems like you're trying to do too much with this. Pick one aspect (preferably epic and release scheduling) and make it work great and delight your users. Then charge less. And create another add-on to do the other more advanced stuff like vacation/resource management. And charge for that assuming that there is value in it. (6) If you haven't already, get your developers out in front of some of your customers who need to use this thing and watch what they do. Don't assume that just because you do software development a certain way that everyone else does too. Note that I wouldn't be so harsh in this review except that you are charging a LOT of money for this and my users hate it, not to mention that one of them hates it so much that he's writing his own app. I'm happy to correspond further about this offline if it would be helpful.
    16 out of 16 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Hey Virginia,

    Thank you for your in-depth review. We're sad to hear that you're having a negative experience with Portfolio. We acknowledge that there's a steep learning curve and some friction in the core user experience - these are areas we have a lot of room to improve.

    Addressing these usability issues, improving onboarding and making it easier for users to understand how Portfolio's scheduling works are major focus areas for us moving forward. We greatly value your feedback as we endeavour to improve these areas. If you're interested we'd be very keen to start a dialogue and schedule a call with you to get your in-depth feedback.

    We're also currently testing a new feature that provides transparency to why issues are scheduled when they're scheduled. It allows you to diagnose all the variables that impact an issue's scheduling and lets you know what the impact of those variables are. From your feedback it sounds like you'd be the perfect case to trial the effectiveness of surfacing this info. For example earliest start date shouldn't be ignored due to release start date - that's not expected behaviour. This functionality would assist to investigate the actual reason the variable was ignored (Sprint assignment should be the only case earliest start date is ignored).

    Please feel free to reach out to my email - rchristian@atlassian.com Look forward to hearing from you.

    Kind regards,

    Rhys | PM - Portfolio for JIRA

    by Aditya Deshpande on 2017-06-23
    Not impressed. I do not need every JIRA user to have access to Portfolio. Only Team Leads and Project Managers. Have to unnecessarily stick to MSP because of this policy.
    9 out of 9 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Hi Aditya,

    Thank you for providing your feedback on Portfolio for JIRA. Our current licensing model is based on the principle of planning as a team activity and to help with transparency across all levels of the organisation. If you have any further questions, I'd be more than happy to discuss in more detail with you. Please don't hesitate to reach our directly: bdavies@atlassian.com

    All the best,Bree

    Pricing

    Pricing details are loading…

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does cloud app pricing work?

    Cloud pricing is subscription based. You are eligible for support and automatic version updates as long as your subscription is active.

    When your subscription renews each month, you are automatically billed for host products and apps based on the number of users in your instance.

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my cloud pricing?

    Apps are billed based on the number of users in your host product. JIRA Cloud apps are priced based on the maximum users of the JIRA products on your instance. For example, if you have JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you pay the 50-user price for apps.

    The pricing structure for cloud products and apps is as follows:

    • Monthly subscriptions with up to 10 host product users are billed at a flat rate price.
    • Monthly subscriptions with more than 10 users are billed per user, starting at the first user.
    • Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.
    • If per-user pricing is not yet available for this app, please contact the vendor for further information.

    If you've opted for annual billing for your host product, apps are also billed annually at a discount (12 months for the price of 10).

    Do you offer academic, community, or open-source licenses?

    Academic, community and open source licenses are not available for cloud apps.

    Can I extend my free trial?

    For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.

    Paid-via-Atlassian pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Apps are billed based on the number of users in your host product. For JIRA Server 7.0 or later, the app tier should match the maximum tier of the licensed JIRA products on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of JIRA Server prior to 7.0, the app tier should match the licensed user tier for JIRA. Even if fewer users want to use the app than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.

    How can I buy apps for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

    • Purchase the app at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the app at the same tier.

    Learn more

    Atlassian provides support for this app.

    Atlassian provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    JIRA Cloud Released 2016-06-07

    Summary

    Seamless integration with JIRA with new live plans!

    Details

    See release notes for details.

    Versions

    Version 2.4.0 JIRA Server 6.3 - 7.4.2 Released 2017-08-08

    Summary

    Program beta improvements, sprint resolution, and other improvements

    Details

    See release notes for details.

    Installation

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Portfolio for JIRA via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Portfolio for JIRA. You're prompted to log into MyAtlassian. Portfolio for JIRA begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Portfolio for JIRA versions compatible with your instance, you can look through our version history page.

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Find new add-ons screen loads.
    3. Locate Portfolio for JIRA.
    4. Click Free trial to download and install your app.
    5. You're all set! Click Close in the Installed and ready to go dialog.

    Similar apps