Roi Fine Atlassian Team

Yes that is correct, in version 2.23 ( released in just short few weeks ) you will have more custom fields types supported other than single line text field. We are adding support to more and more types incrementally as each type demands development work. Does that make sense?

Hi @Brian, Thanks for your feedback, great to see your team is already up and running with the new experience. We are adding support to custom fields in Portfolio incrementally. In the next few version updates you can expect to to view and edit single select, multi select and number custom field types. Would be great to…

Hi @Rahul Savaikar, The target start/end values are stored in the entity_property database table. It is a different table where other Jira custom fields values are stored. Please let me know if that helps, Best,

Hi @Caitlin Jonesler, Thanks for your detailed use-case. One way you can bridge the gap in estimation detail between middle management & dev. teams is by using target dates to initiatives and epics to represent a certain size of expected time. Dev. teams could use story points for stories. Would that work for you? Cheers,…

Hi Mitch, The new planning experience update is only available for server/DC customers. Please let me know if you got any questions. Best, Roi Fine | Product Manager | Portfolio for Jira Server/DC

Hi Caitlin, There is no ability to map story points in Portfolio to custom fields. Can you please explain why using the story points field won't work for you? You can always submit a feature suggestion ticket here. We review the tickets often when prioritizing our roadmap. Please let me know if you got any question, Best,…

Hi Sarah, There are many ways to setup your projects structure, so in the end, the best way is what fits your organization. First, I would recommend you to create an initiatives project in Jira to contain your big & important projects ( issues above epic ). See doc…

Hi Ariane, The Cloud version has the 5000 issues limit as well. A way to workaround the issue limit is to reduce the number off issues you'd like to view in your plan. A good way to do that is either by creating filtered boards in Jira and source these boards to Portfolio or alternatively create custom issue filters in…

Hi @Fernando, Thanks for raising these problems. Please allow me to share my teams thinking and plans: Global availability across multiple plans is not in our short-medium term roadmap. We understand it's a need but at the moment we are focusing on making the planning experience as complete and delightful within a plan. In…

Hi Pavel, Yes, it is still possible to create multiple Portfolio plans. We are working on a fresh new capacity, our first iteration will have the availability and utilization of a team bounded within one plan. Please let us know your thoughts, Cheers, Roi | Product manager | Portfolio for Jira 

Hi @Nick Zigomanis, Our goal is to help you and your organization plan and track work across team of teams. We are aware that every company has different data set and way of working in Jira. One of the biggest changes we made in Portfolio's new planning experience is that the automatic scheduling is optional. That means…

Hi @Jovanna Pugh, This sounds like a bug to me, please contact support and submit a ticket here: https://support.atlassian.com/contact/#/ I hope that helps,

Hi Murty, Can you please raise a support ticket with your inquiry? Our support engineers will be happy to help you. https://support.atlassian.com/contact Thanks,

Hi @Deepak Shama, It sounds like your use case can be solved by using the program feature. The idea is: * Each set of projects can be sourced to a plan. * These plans can be grouped to a program - a high-level view that helps you track status and progress across multiple plans in Portfolio for Jira. I hope that helps, Roi

Hey Mike, Sorry to hear that. As a product manager of Portfolio I want to make things work for you. But as you may know, each company & teams have a different way of work. On top of that, each team often has a different way to work in Jira. This is a challenge for an app that sits on top of Jira. Our thinking and approach…

Hi Ricky, Thanks for your inquiry. Adding/customizing an issue hierarchy between epic to story is not in our short term roadmap. I created a feature suggestion ticket to capture the terminology gaps of scaled agile frameworks(and any customized solution) with the Atlassian product line. We are prioritizing our roadmap…

Hi Kristof, I understand how annoying is not finding a "done" issue in your plan. I want to clarify that Portfolio for Jira is a forward looking roadmap tool. It doesn't have dedicated views for past reference. You can express your views and needs in this ticket: https://jira.atlassian.com/browse/JPOSERVER-1267 We might…

Hi @[deleted], If a issue has children (e.g. initiative with some epics) then the rank of the parent becomes the rank of its highest-ranked child. The reason for that is that we want to make the parent rank represent what will be done first, if the top story of an epic is ranked last this epic will be scheduled last so it…

You can always add additional issue types to an existing project. This document will assist you along the way: https://confluence.atlassian.com/jiraportfolioserver/configuring-initiatives-and-other-hierarchy-levels-802170489.html Cheers,

Hi guys, There was a similar discussion around how to structure "higher up" issues such as initiatives in Jira & Portfolio. You can check it out here Cheers,

Hi @Nicole, Portfolio doesn't have a dedicated report for team's leave but we released a new team management API in beta. With the API you could either populate or extract team management data programmatically. Check out the docs here Please let me know your thoughts, Cheers,

Hi Arun, This is possible with a new JQL introduced in Portfolio for Jira 2.11 server version. To get a result of any parent issue of an issue in a specific hierarchy level, type issuekey in parentIssuesOf("EX-000"). This should be done via JQL in JIra. Find out more about all special JQL functions related to Portfolio &…

Hi @apusysadmins, This is an expected behaviour. A program is a high-level view that helps you track status and progress across multiple plans in Portfolio for Jira. Practically, it shows you all initiatives(and higher up issue types) status break down down to the epic level. Taking performance considerations we decided to…

Hi @Liandro Rossini, Thanks for your reply, this functionality you talk about, is currently not available. There is a feature suggestion captured here that talks about the notion of "parked" issues. I assume that could apply for your usecase. You could either raise a feature suggestion or add your vote & comment for the…

Hi @Liandro Rossini, I'm a product manager in the Portfolio for Jira server team. I understand your problem. In order to auto-schedule issues on the timeline, Portfolio needs issues to be estimated. You can use the default estimates feature if your teams do not tend to estimate well in advance. More info here:…

Thanks @Cameron Eldridge, much appreciated!

Thanks @Mike Winston This helps a lot!

Hi Stephan, That is a great question. Releases is a good way to visualize value shipped for customers. If you have different dates for capabilities completion and releases you could use a creative solution of a parent issue. I.e: If you create a parent issue for all issues that relate to "user able to login" you could…

Hi William, That's a good question. It would be great if you could attach a screen shot of the 2 situations you are describing. The dynamic date should change according to the amount of work you got planned and the team's velocity. Cheers,

Hi Pepper, A plan is a container with multiple Jira projects. A program is a high level view that groups multiple plans. You could link some/all of your plans to a program and use the program view filters to see different sets pf plans. Let me know if that works, Cheers