Roi Fine Atlassian Team

Hi @Martin Schwaiger , My name is Roi, a pm in the team. We will soon ship the ability to set different capacity to future sprints (scrum team), and weekly iterations (kanban teams). It's a matter of weeks so stay tuned. Roi

@Arash Ghazvini , we will be looking to bring this feature to cloud customers (Jira Software Premium) as well. I can't say exactly when, but soon 😊

Hi @[deleted] What could work is setting up a JQL filter that would look like PROJECT IN (A, B, C) AND "Parent Link" IS NOT EMPTY and using that JQL filter as the issue source. This would solve most of the cases but not the case of a story belonging to an epic that does not belong to an initiative. For that, you would need…

Hey Robert, no worries :) I know there is a lot of change form the old version, but we believe it's only for the better. The new UI introduced in version 3.0 is much simpler and intuitive to plan with. * Here is a page that describes the changes in functionality * If labels and components are used for miscellaneous you can…

HI @MHB My name is Roi, a product manager on the team. In regards to reporting, the way it works is that you'll need to filter, group, color the Roadmap tab. Then, you can save it as a view (version 3.23 and forward) and/or share it as a report via a link or a confluence macro (export is coming soon). You can basically get…

HI @Rob Horan , My name is Roi, a product manager on the team. In regards to reporting, the way it works is that you'll need to filter, group, color the Roadmap tab. Then, you can save it as a view (version 3.23 and forward) and/or share it as a report via a link or a confluence macro (export is coming soon). You can…

Thanks @Matt Doar , glad to hear your teams find this feature useful. It is available for all users since version 3.23. Fire any feedback you might have. Cheers!

Sure @Nidhi Gupta , when you go through the create plan steps you must have less than 5000 issues in your plan. But after the plan is created you can have more than 5000 issues. I.e. You can create more issues in your boards/filters/projects. Does that make sense? I'd be happy to chat about your use case if you're…

Hi @Ashkan Malekly , I'm glad you're finding the new rollup feature useful. By the way, it's now available to everyone and not only for early access. Regarding the problem you are describing, I would advise you to contact EasyBI support. A potential reason you can't export the target dates easily could be that target dates…

Hi @Katerina Zacharakis , Thanks for your feedback. Try to group by a team and see if it works, make sure the teams' are collapsed. You can also check the docs here: https://confluence.atlassian.com/jiraportfolioserver/understanding-team-capacity-974360319.html Roi

Hi Argyro, To help you I would need to know which issues are you missing - What type/hierarchy? Portfolio categorizes issues by the standard names but other types are still mapped and can be created within the Plan UI. I.e: Bugs would appear under the Story category. Roi

Hey Harry, You can also try: 1. In the Jira issue screen UI use keyboard shortcuts - press "." > type epic link 2. In the Portfolio UI - You can Drag and drop bugs to epics in the scope list or use the parent field in the fields section I hope the above makes sense, and you'll find your prefered way to link child issues to…

Interesting stuff, thank you. I'm still not sure why you would need two fields and not one. Is it for the sake of program increments reporting? 

Hi Justin, I'm sorry but you can't map fix version to a custom field. I'm curious to learn why you prefer a custom field over the fix version field. Cheers, Roi

Soon @Mohsen Mehrafrouz :) I can just say that we're working on it. Roi

Hi @Bertran de Boer , I'm a product manager on the team. We decided not to prioritize individual capacity in the new interface. We believe empowering our customers to focus on teams' capacity rather than individuals would be more beneficial. We believe focusing on teams' capacity is less effort for planners, enables…

Hi @Tere Pile , The roll-up dates feature is available for Server/Data Center customers of Portfolio for Jira. This feature is not currently available in Cloud. We currently have a beta for a similar experience for cloud customers. You are welcome to apply to portfolio-cloud-beta@atlassian.com. Please include your site…

Hi @sharmila.patwardhan , Good question. I'll try to help. A Portfolio plan is an editable view of your work in Jira. The view is defined by the plan's issue sources. In your example, I suspect that one plan doesn't have the right issue sources. Make sure to add the issue source with your initiatives. Here are some related…

Hey @Andrea Urban , The roadmap of Portfolio for Jira varies between deployment options. Are you a Server or Cloud customer? Cheers,

Hi @diego smith , We are working on a feature for Portfolio for Jira Server/DC that could help you. Stay tuned. Cheers,

Hi @rberkel We are working on a new feature that would allow you to adjust your future velocity per sprint to accommodate such cases. Please stay tuned, it would be available soon. Cheers, Roi | Product Manager - Portfolio for Jira

Hi @Ray Gorbea You raised a good question that has quite a few possible causes. I'll note all/most of them here. The Portfolio plan shows you a different amount of issues than your JQL filter because you may have: * Filter permissions: Is the filter you are using shared with other users that try to access the plan? * The…

Hi @Wendi Pannell , I'm a product manager in the Portfolio team. Could you please explain me the problems you are facing? I'll be interested to know: 1. Which version of Portfolio are you using? 2. How did you add the initiatives? Did you create a Jira Project for these? 3. Did you follow our getting started…

Hi @Dimitri Honlet , I would strongly recommend adopting the new interface. But you can still filter completed issues in the older interface. * Go to More (top Portfolio Scope navigation bar) > Completion date. * Select which filtering time frame you'd like to use for completed issues. More…

Hi @Dimitri Honlet , To set how long to display completed issues: * In your plan, click settings ( ) > Configure > Issue sources. * In the 'Completed issues' section, enter the number of days you want to keep completed issues in the plan. More here…

Hi @Barbara Kok , My name is Roi, I'll be glad to answer any questions you may have. Please use this link to book time with me. https://calendly.com/rfine/60min Cheers, Roi Fine | Product Manager | Portfolio for Jira

Hi @Gil Groman , yep it should work. Please contact support to report this here: https://support.atlassian.com/contact/

Hi Chris, My name is Roi, and I'm a product manager with the Portfolio for Jira team, I would love to learn more about your problem so I can help you. Would you like to jump on a call? You can use this link: https://calendly.com/rfine/60min Cheers, Roi Fine | Product Manager

Hi @Gil Groman , Are you using the old or new interface of Portfolio for Jira Server (3.x)? If it's the new interface, at the moment there is only default number to reflect velocity, hence no way to reflect diminishing or rising velocity/capacity. We are working on a new feature that would allow you to adjust your future…

Hey @MikaVesalainen , No worries. > But in our case there are some teams that implement increments in multiple Projects. You can create a board that has issues from different Jira projects. Please see this previous community post…