Dave Atlassian Team

Thanks @Lyle Hayhurst - we looked into various options for pre-entering data to assist with matching filters and that might be something we implement in the longer term. But for now our short term solution is going to be to provide a warning. Unfortunately it's always a case of weighing up the relative priority and…

Hi @Roberto Luces , To be honest I'm not very familiar with the Rich Filters for Jira Dashboards plugin (I'm assuming this is what you're referring to). However, you might be interested to know that in 3.10.0 of Portfolio that we released this week we've added support for the Portfolio team field to be included in Jira…

Hi Lyle, Thanks to the feedback, much appreciated. One option is to use the share button to create a shareable link to the plan. This link will include a URL request parameter the maps to the view configuration that there are shared (including the filters set). The only limitation of this is that when you open the URL you…

I'm a team leader for Jira for Portfolio Server. Thanks for raising this issue, this looks like a regression in our functionality and I've raised internal issue to fix this problem. Unfortunately I can't commit to a future version when this problem will be resolved. Regards, Dave

Hi, I'm a team leader for Portfolio for Jira Server. This is something that we're going to be resolving in a future release portfolio. At the moment the view settings (including filters) are only persisted to local storage each browser. In the future it will be possible to create a number of views each plan (including…

@[deleted] : * Velocity is not automatically pulled in from previous sprint boards in Jira. This is something we would ideally like to add but is not something that is on our immediate roadmap. For the time being you'll need to manually add your teams velocity * The restriction on not being able to use Kanban teams in a…

@Chris Thomson Exports (including PDF and CSV) is something we're going to be looking at introducing in the near future, unfortunately I can't commit to any specific dates or releases but we recognise that we need to make it easier to consume the data and roadmaps from plans created in Portfolio. 

Thanks Pavel and Scott, we appreciate the feedback. We're continuing to iterate on the 3.0 release and you should continue to see new features (and improvements to existing features) rolled over time (we have a new release approximately every 2 weeks). We know that there are definitely areas of improvement to be made in…

Hi Bruno, It shouldn't actually be necessary to save the changes to Jira, however I do know that we had some issues with the estimates fields not triggering a refreshed calculated schedule (we cache old calculation results if we don't believe any data has changed) caused by a failure to recognise that the field value has…

Hi Bruno, The default working hours for a day is considered to be 8 hours. So if you have an issue that is expected to take 10 days then it's assumed to take 80 hours of work. If your team works 40 hours a week then it would be expected to take 2 weeks of work. It is assumed that regardless of team size that only one…

Hi Gianluigi, I'm sorry you've experienced this problem. In order to help answer the question maybe you could provide some additional information. * Which version of Portfolio are you using? * What planning experience are you using (Live Plans or the new planning experience introduced into 3.0)? * What actions are you…

Hi, A plan will show any open issues that match the configured issue source along with any closed issues that have been closed recently. In the new planning experience (introduced in Portfolio 3.0) "recent" means in a configurable number of days (the value defaults to 30.... so issues that have been closed within the last…

Thanks for the clarification.

OK, that's really interesting - then this is a slightly different problem to what we've encountered ourselves. So as soon as you try and group by team again it crashes? Which version are you using?

Now that you've cleared local storage you should be able to use it again now and you shouldn't hit this problem whilst you're on the version that you're on. There's a strong possibility that now you've cleared local storage this time that you won't be impacted by this in the future. What we're going to be doing is to make…

I'm really sorry to hear that you've encountered this problem. Can you try clearing the local storage for your browser as this should resolve your problem. For example in Chrome * Press F12 to open the Developer Tools * Click the "Application" tab * Expand the "Local storage" twister toggle * Select the domain where your…

Hi Kelly, A release is used to group a collection of issues that is usually mapped to a specific version of the the product associated with the project you're working on. It is not essential to use releases. For time boxing you should ideally configure a scrum team board for your project and use it to create sprints. These…

Hi Georgii, Thanks for raising this point. You're right that this is a problem with the dependency validation logic in the UI being too aggressive. This will be resolved before we GA the new planning experience such that if the issues are assigned to the same sprint that they will not show dependency warnings in this…

Hi Aishwarya, In Jira server it is possible to configure the type of custom field to be a text area rather than a text field. I'm not sure if this is possible in Jira cloud though - definitely worth checking though, Regards, Dave

Hi Aishwarya, If you're using Portfolio for Jira Server I would recommend that you add a custom text area field and then configure Portfolio to display that custom field. You can find information on adding custom fields to Jira here (you may need to select the correct version for your Jira instance). You can find…

Hi Samuel, This response may be too late given that the date for your presentation has passed. Also, unfortunately it's not entirely clear what information you needed. It's worth being aware that the the Jira Cloud and Jira Server are now separate products (see here for more information) and similarly Portfolio for Jira…

Hi Dania, I guess this depends upon how realistic you're expecting the scheduling to be. For example if you're creating a team per idea but each real team can be working on multiple ideas then there's a risk that you could be overloading teams. If this is a way of establishing relative effort between the ideas then this…

Hi, There is no difference in limits between the trial and full versions of Portfolio. There are limits as to what you can add for a plan - the details can be found here: https://confluence.atlassian.com/jiraportfolioserver/creating-and-deleting-plans-802170502.html I would however be interested to know more about how you…

Hi Dania, To help answer your question it would be useful if you could provide a bit more information. Are you looking to actually assign the issue to multiple teams and have the multiple assignment taken into consideration by the scheduling algorithm when you click "Calculate"? If that is the case then there is no…

Hi Mikkel, It looks like you might be experiencing the same issue described in this threads: * https://community.atlassian.com/t5/Jira-Core-questions/The-item-is-assigned-to-an-invalid-sprint/qaq-p/319548 * https://community.atlassian.com/t5/Portfolio-for-Jira-questions/Invalid-sprint/qaq-p/1852 At the time of answering…

One possibility here is that the default team working hours is being used to calculate a date indicating that the task can be completed in less time. So for example your task might take 40 "person-days" but the default team capacity 200 weekly hours (e.g. 25 person days per sprint). One thing you could try is changing the…

Hi @Luke Burkey, When you start a sprint in Jira you can actually provide the start date. I would suggest that you start the sprint with the date you actually plan to start working on it. I've tested this in my local Portfolio instance and have verified that Portfolio correctly uses the start date of the sprint that I…

Hi Russ, The reason that this occurs is that the scheduling algorithm works on the principle that a sub-task can only be implemented by a single person. This is why it is not possible to use sub-tasks in this way. Unfortunately it is not possible to relax this constraint. Regards, Dave

What version of Portfolio are you using? This looks similar to this issue (https://bulldog.internal.atlassian.com/browse/JPOS-387) that was fixed in version 2.8.0.

Hi François, Thanks for asking this question. I just wanted to verify the behaviour that you're experiencing - I think what you're saying is that there is no way to "undo" changes made to a plan after you click the calculate button? (Portfolio won't ever automatically commit any of the changes to Jira issues until you…