Bree Davies_kv5afn Atlassian Team

@Edmund Munday - not a dumb question! We don't support that just yet, but we're working on it. Coming soon!

Hi Vinay, thanks for the feedback - we'll definitely take this on board. Cheers, Bree - Jira PM. 

@Romy Lindenberg we can't give specific timings unfortunately but I can say that it's very highly prioritised, so stay tuned :) - Bree, Jira Software PM. 

Hi @Mike Solomon and @Simeon G - we have this feature very highly prioritised, so stay tuned! 

@Henrik Öquist Thanks very much for your feedback - we really appreciate it. 

@Mahmoud Elmashad Thank you for your feedback. With regards to keeping an eye on issues and epics at the same time, what was the most important piece of info you took from seeing epics as well on the backlog? We're working on bringing colour back soon - stay tuned :) 

Hi @Sam Storer - not at this time. Your feedback is important to us - thank you for sharing this wiht us. 

@James Fleming apologies for our delayed response. The new roadmaps feature is only available in next-gen projects. If you are using a next-gen project, then you'll see the roadmap icon in the navigation. I hope this helps :) Cheers, Bree

Hi @Chuck Foster - unfortunately we have no plans to bring this to classic at this time. What are the features you're currently waiting on in next-gen? Thanks, Bree

Hi @Chuck Foster We've just released a new (and free!) roadmapping feature in the new Jira project experience. It only displays epics but could be worth a try to see if it meets your needs. Find out more here. Cheers, Bree

Thanks for your feedback @Michael Wilkes - really appreciate it. We'll take this on board. We'd love to know more about your first impressions on using the roadmap. Would you be open to chatting with us in more detail about your experience? Please reach out to bdavies@atlassian.com if so. Thank you! Bree. 

Hi Brett, I'm Bree - a PM on Portfolio. Please feel free to send me an email (bdavies@atlassian.com) if you'd like to chat more about Portfolio. Your local AUG is also a great idea. Thanks for your feedback on improving our dependency visualisation too :) Cheers, Bree

Hi Tal, It may be easier to progress this one if I'm able to see your plan and how it's been configured. My email is bdavies@atlassian.com - are you open to a video call so we can have a closer look? Thanks, Bree

Hi Tal, In this case we have a mix of 'strict' assignments which Portfolio is trying to respect (your release assignment and also team member assignment) combined with what you actually want to reflect on your schedule, which is your target start and target end dates. Some ideas: * If you change your issue assignee import…

Hi Tal, A Jira story and a Portfolio story should be one and the same. You could use skills to represent the different teams as you've mentioned. The nuance in the error message is 'available' team members. Do you have any team members with upcoming availability constraints? (For example, have you set up any future…

Hi Oscar, First of all, I'm sorry that you've been frustrated! What do each of your board filters look like? Issues can 'disappear' from Portfolio if they no longer match the board filter that's associated with your plan, which I suspect is the issue here. After you commit, do you see any kind of message along the lines of…

Hi Oscar, What is the date range associated with this particular release? Thanks, Bree

Hi Michael, If you look at your scope table issue order (when all sorting is turned off), is the story order as you'd like it to be? 'Priority' of issues is derived from the story level, so give this a check and make sure they are in the order of priority you want. I would also recommend making manual release assignments…

Thanks Tal, this is all really fantastic feedback for us (especially the context of why!). Would you rank your priority of these features in the order you've responded above? Thank you! Bree

Hi Tal, Is it possible to move your 'story' up a level of hierarchy to be an epic? Then, you could have the behaviour you're after - where you can create stories per team (and assign them as you need) and have the estimate sum at the parent (epic) level. Please let me know what you think. Cheers, Bree

Hi Tal, Is it possible to remove the dummy version assignment just for this issue? Without this, we'll apply the target start and target end dates you've also added to the issue and you'll be able to 'force' the dates as you'd like (assuming you also don't have an estimate on the issue). In addition, inside your plan…

Hi Tal, The Cloud team has a separate release cadence and roadmap to the Server team. However, I'm really interested to understand which of these features you would like to see in Cloud and why? Your feedback will be an important input to our future plans. Thanks very much and look forward to hearing from you, Bree

Hi Nancy, You're right - the board filter is extremely important for Portfolio. If this changes regularly, Portfolio will always reflect the source of truth in Jira - which comes back to the issues which match the board filter query. If the board filter does change, Portfolio will simply reflect these changes. So for…

Hi there, You can go back in time (beyond the current sprint) to include releases / issues which may have been closed in the Themes report. Just make sure you click on 'More' as per below: Then by choosing 'Scheduled Range' you can input your own date parameters if you select 'Specific Range'. You can choose the date range…

Hi Stephane, Correct - you will need to have set dependencies between issues within your plan, and for these dependencies to be included in your schedule, in order for them to be reflected within the Dependencies Report. Looking forward to hearing your feedback on the report! Thanks, Bree

Hi there! I'm not quite sure what you mean by 'make a change in the portfolio plan'. Are you able to explain? Are you not seeing it as available yet in your report drop-down? Thanks, Bree

Hi Stephane and Steven, Bree here - I'm a PM for Portfolio for Jira. We've just released the new Dependencies Report, which will hopefully help with some of the dependency visualisation / management issues you've mentioned above. It allows you to see all the issues in your plan which have a dependent connection between…

Hi all, Just letting you know that parallel sprint support has now been added for Portfolio for JIRA cloud customers. You can now assign an active (or conflicting) sprint to one or many teams, as well as assign future sprints to teams via the team card. You can find more information and documentation here:…

Hi Jussi, There is an easy workaround in JIRA for this. For work that is not ready to be worked on (so you don't want it to be scheduled into any kind of Portfolio plan) use a label to denote it as 'not-ready' or a certain status. Or conversely, if you could label issues that are ready with a 'ready-for-dev', if this is…

Hi Connie, Was sprint 1 active when you were trying to make these changes? I ask this because Portfolio will never automatically schedule work into a sprint that is already in-flight, this always needs to be done manually if it's what you're trying to achieve. Also it looks like you're trying to manipulate the scheduling…