10,234
Customers have installed this app in at least 10,234 active instances.
10,234
Customers have installed this app in at least 10,234 active instances.
10,234
Customers have installed this app in at least 10,234 active instances.
    by Atlassianfor Jira Cloud, Jira Server 6.3 - 7.12.2, Jira Data Center 7.2.0 - 7.12.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

    Supported
    Atlassian supports this app.

    Get support

    The agile roadmapping tool, built for Jira Software

    The agile roadmapping tool, built for Jira Software

    The agile roadmapping tool, built for Jira Software

    Create agile roadmaps connected to work in Jira

    Track projects and easily share status

    Connect your strategy to execution

    * Get a visual timeline of your Jira Software work issues and see when your releases will ship

    * Create different versions of your roadmap in a sandbox environment

    * Push changes back to Jira Software when you’re ready

    * Get a read on your team capacity with Portfolio’s capacity report

    * See all dependencies across projects and teams and prevent unnecessary bottlenecks

    * Track progress of your releases and Jira Software work issues

    * Ensure your epics & stories map back to higher levels of hierarchy

    * Quantify attention given to different areas of your roadmap with themes

    * Get visibility into work across projects & teams at any level of hierarchy

    Create agile roadmaps connected to work in Jira

    Track projects and easily share status

    Connect your strategy to execution

    * Get a visual timeline of your Jira Software work issues and see when your releases will ship

    * Create different versions of your roadmap in a sandbox environment

    * Push changes back to Jira Software when you’re ready

    * Get a read on your team capacity with Portfolio’s capacity report

    * See all dependencies across projects and teams and prevent unnecessary bottlenecks

    * Track progress of your releases and Jira Software work issues

    * Ensure your epics & stories map back to higher levels of hierarchy

    * Quantify attention given to different areas of your roadmap with themes

    * Get visibility into work across projects & teams at any level of hierarchy

    Create agile roadmaps connected to work in Jira

    Track projects and easily share status

    Connect your strategy to execution

    * Get a visual timeline of your Jira Software work issues and see when your releases will ship

    * Create different versions of your roadmap in a sandbox environment

    * Push changes back to Jira Software when you’re ready

    * Get a read on your team capacity with Portfolio’s capacity report

    * See all dependencies across projects and teams and prevent unnecessary bottlenecks

    * Track progress of your releases and Jira Software work issues

    * Ensure your epics & stories map back to higher levels of hierarchy

    * Quantify attention given to different areas of your roadmap with themes

    * Get visibility into work across projects & teams at any level of hierarchy

    More details

    Made by Atlassian and speficially built to work with Jira Software.

    Portfolio for Jira helps you build a plan, see the big picture, track progress, and easily share with stakeholders.

    Check out some of our helpful resources for getting started:

    More details

    Made by Atlassian and specifically built to work with Jira Software.

    Portfolio for Jira helps you build a plan, see the big picture, track progress, and easily share with stakeholders.

    Check out some of our helpful resources for getting started:

    More details

    Made by Atlassian and specifically built to work with Jira Software.

    Portfolio for Jira helps you build a plan, see the big picture, track progress, and easily share with stakeholders.

    Check out some of our helpful resources for getting started:

    Reviews for cloud

    (174)
    Sign in to write a review
    by Trace Wilkerson on 2018-07-31
    I approached Portfolio simply for hierarchical project tracking. I really liked what it has to offer. Unfortunately there are some big red flags. Why isn't hierarchical project management built into Jira natively? As a product owner myself: If I realized a feature was valuable enough to charge for, I would use that as competitive advantage in my original product, not build an add-on that has its own pricing model. (seems like shady sales strategy) We are small, around 30 Jira core users, the Portfolio pricing for 30 seems ridiculous considering only myself and maybe one other person would see/use the features added by Portfolio. Not worth it for a feature that should really be in the application by default. Unfortunately, we'll be looking for an alternative or building an alternative to Jira as the user experience is clunky to the point where managers have to force developers to use it for tracking (the developers don't feel like adding their stories and tasks in Jira make them more productive). My review is for my team and our use case. It clearly can not reflect or determine other teams' experiences with the product.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Chris Doyle on 2018-06-27
    We are in the process of closing our portfolios and removing this module. It is very pretty, and potentially extremely powerful. The delivery is absolutely unuseable. I have had 2x robust discussions with Atlassian product managers about all of the problems in this module - haven't heard anything about progress - I guess only when customers stop paying for this will they care. This is a massive missed opportunity, as this module could be so good. The scheduling algorithm, per other reviews, thinks it is smart, is not, and you cannot either review the decisions it is making, nor force it operate how you require. The themes report keeps telling me data that is incorrect - I cannot drill in and see why, I have reviewed every single item in the portfolio and the data does not match. The ability to manage teams was useful - except I can't manage split resources and variable work rates properly. You can't see or manage priority in this module. This is absolutely critical. I would go on but there's no point - just don't waste your time or money on this, it will not provide value.
    11 out of 11 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Hi Chris,

    We appreciate your honest feedback and the conversations we had about Portfolio for Jira. We are working hard to improve the experience and the frustrations you have called out here - your insight was invaluable for us and we listened very closely. We are sorry to see you go and hope you'll give Portfolio another try in the future.

    Thanks again,Bree

    by Alexander Schwantes on 2018-04-08
    I read the reviews and thought I would give it a go as my use case might be different. I was wrong. Overall it kind-of looks like does what you expect, but not really. It feels like its developed by someone completely different who hasn't followed Atlassian norms and conventions. The scheduling plain and simply doesn't work as it tries to do things automatically for you with stupendous results that you can't override. * The size of the bar in the fake "gantt' scope chart is not actually representing the story points on an epic. Portfolio has estimated that an epic with 5 story points will take 8 months to complete and made it really long in the scope graph, while another epic with 145 story points it thinks will be done in 2 weeks. There appears to be no way to adjust this either. Portfolio is trying to be too smart and just ruining everything. * why can't I adjust things from the scope graph? * Everything MUST be in a release, even epics/tasks for the distant future. I can't assign Later to some issues, it just doesn't work. Such a pain. Had to create a dummy release in the future and put epics in that. * Can't undo with Ctrl Z, is a complete pain to undo something * Clicking on an issue in the scope table shows a details view that is unnecessarily wide, making the list of tickets in scope now feeling squashed. * Images don't show on issue detail in the scope table so you always have to click out of the planning to view the issue attachment * Can't view dependencies in the scope table so its unclear exactly what ticket is linked * Issue detail view: Warning "The people working on this issue are overbooked for this sprint" yet it doesn't show you who is booked on the ticket. thaaanks...? * Clicking on a release in the scope view does nothing.. seriously.. * Release scheduling is plain broken. Release 1 is set to start before release 2 and is in front of it for the development, however in the scope graph, release 2 is shown as being before release 1.​ * Issue dependencies don't show their status. In Jira if an issue is blocked by another issue and that issue is closed, it is displayed with a strike through it​ and the status closed. But in Portfolio, every blocked issue appears as if its still open, completely breaking Atlassian convention
    18 out of 18 found this review helpful
    Was this review helpful?YesNo
    Atlassian

    Hi Alexander,

    Thank you for providing your honest and detailed feedback here. We pay close attention and will be taking this all on board for future improvements of Portfolio for Jira. We're sorry to see you go.Best wishes, Bree

    by Long Dang on 2017-10-26
    I cannot use the trial Portfolio plugin with trial Jira. After installing the Portfolio plugin successfully, when I try to create a plan then the msg below appears "You have not yet licensed Portfolio for Jira. Please get a free 30-days evaluation license or purchase a new license in the Atlassian Marketplace and try again. If you think this message is wrong, please contact your Jira administrators." At this time I cannot disable/uninstall/configure Portfolio plugin because there is no such those buttons.
    8 out of 9 found this review helpful
    Was this review helpful?YesNo
    by Elector Masarakufa on 2017-10-05
    We have just started using Portfolio and the most frustrating thing right now is when looking at the gantt view - the scheduling algorithm ignores our target dates as well as the earliest start constraint! So when we need to check capacity for the team - its giving the wrong info. Is there any way we can work around this? Another thing - none of the dates already added on a jira board are pulling through in Portfolio such that we have do add dates all over again which is rather frustrating! Not very user friendly......
    7 out of 7 found this review helpful
    Was this review helpful?YesNo

    Reviews for server

    (174)
    Sign in to write a review
    by Rakesh Navagale on 2018-08-31
    While upgrading it makes JIRA performance very very slow. - Rakesh
    Was this review helpful?YesNo
    by Justin Freeman on 2018-06-20
    Keeping it current with the latest JIRA Server release would be good. JIRA 7.5 is out. Latest supported version is 7.2.11.
    6 out of 7 found this review helpful
    Was this review helpful?YesNo
    by Nico Paffen on 2018-06-20
    The tool fullfils a lot of our needs, however as only 200 - 300 users (max) are going to use it the tool is very expensive regarding the 10.000 tier license for JIRA we have. There should be an option for this kind of add-ons (with this price setting) to disconnect from the amount of JIRA licenses. Otherwise too many customers will not be able to make use of this valuable tool.
    5 out of 5 found this review helpful
    Was this review helpful?YesNo
    by Christian Haintz on 2018-02-27
    Good tool!
    0 out of 4 found this review helpful
    Was this review helpful?YesNo

    Reviews for Data Center

    (174)
    Sign in to write a review
    by Francis Lowry on 2017-09-03
    Does not work with Jira core
    7 out of 9 found this review helpful
    Was this review helpful?YesNo
    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.
    7 out of 10 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 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.
    33 out of 33 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.
    46 out of 46 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.
    14 out of 14 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

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    10 users$1025 users$99050 users$1,820100 users$3,300250 users$6,600500 & upAdditional pricing details
    50 users$910/year100 users$1,650/year250 users$3,300/year500 users$4,950/year750 users$7,150/year1000 & upAdditional pricing details
    Up to 10 users
    $10
    monthly flat fee
    Free 30 day trial
    11 - 100 users
    $3.50
    per user/month
    Free 30 day trial

    Pricing FAQ

    How does cloud app pricing work?

    Cloud apps are sold as a monthly or annual subscription. 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 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 Atlassian 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 apps is as follows:

    • Monthly subscriptions with up to 10 Atlassian 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 you've opted for annual billing for your Atlassian 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 for cloud apps?

    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.

    Pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 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 Atlassian 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 Atlassian product. For Jira 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 (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira 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.

    Can I install this app in a Data Center product?

    Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app has a Data Center approved version, you should purchase a Data Center license for the app.

    If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.

    Learn more about Data Center licensing

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

    For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.

    Community and open-source licenses are available for server apps. Learn more about community and open source licenses.

    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 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

    Pricing FAQ

    How does Data Center app pricing work?

    Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.

    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 Data Center pricing?

    Apps are billed based on the number of users in your Atlassian product. For Jira 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 (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira 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.

    Can I install this app in a Data Center product?

    Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app has a Data Center approved version, you should purchase a Data Center license for the app.

    If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.

    Learn more about Data Center licensing

    Do you offer academic, community, or open-source licenses for Data Center apps?

    For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.

    Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.

    Can I extend my free trial?

    For Data Center 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 product, and you're all set.

    Atlassian provides support for this app.

    Atlassian provides support for this app.

    Atlassian provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    Community

    Community discussions connect you to the vendor and other customers who use this app.

    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.

    Vendor support resources

    Documentation

    Find out how this app works.

    Community

    Community discussions connect you to the vendor and other customers who use this app.

    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.

    Vendor support resources

    Documentation

    Find out how this app works.

    Community

    Community discussions connect you to the vendor and other customers who use this app.

    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 2017-08-29

    Summary

    Dependencies report, scheduling factors, and sharing program reports

    Details

    See release notes for details.

    Versions

    Version 2.17.0 Jira Server 6.3 - 7.12.2 Released 2018-09-11

    Summary

    Updated Jira issue events for Portfolio custom fields, Portfolio now DC approved

    Details

    See release notes for details.

    Versions

    Version 2.17.0 Jira Data Center 7.2.0 - 7.12.2 Released 2018-09-11

    Summary

    Updated Jira issue events for Portfolio custom fields, Portfolio now DC approved

    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.
    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.

    Similar apps