Rhys Christian_7so9sa Atlassian Team

Hey Toolie, Firstly I'll just let you know that can just use the sub-tasks for story points and roll it up to the story level. If I understand correctly the main problem here is you're not seeing Progress on your story rolled up from the sub-tasks? This is likely a filtering issue on your plan. Click the More button next…

Hey Radford, Once a team has been shared it can only be deleted from the Shared teams and people page. Click on the Portfolio drop-down and click Manage Shared Teams. To delete teams simply click the 'x' on the top-right of the team. Note that when you share a team you cannot un-share it.

Hey Mike, I should've also mentioned that this only works at the story level and will not work for issues that span multiple sprints. Issues will also not be able to be assigned to an active sprint as that requires an explicit change to the active scope. So try going to the story level and assign the particular stories to…

Hey Mike, Thanks for the screenshots they help to clarify. It looks like you're actually clicking the capacity bar in those screenshots which is why the option wouldn't appear there. * Make sure you've selected Schedule in the drop-down. * Click on the cog next to the drop-down and click the checkbox for sprint (I…

Hey Michal, Once issues have been calculated for a sprint you can assign those issues to the sprint by clicking on the sprint name. E.g: image2017-2-22 10:50:41.png Note that the sprint needs to exist in the backlog for this to work. Please let me know if you have any more questions about this. Cheers, Rhys

Hey Jyotiprakash - This is quite an interesting use case. Could you please explain how you use Portfolio if not for calculating a schedule? We’re glad that you’ve find a use for Portfolio without needing to use calculate however it’s not usage we want to promote by having an option to disable that button. The best…

Hi Anders, Portfolio 2.0 has replaced the import workflow with an "Issue source" model. The issue sources are the projects/boards/filters that you define as the issues to bring into Portfolio and remain synchronized with JIRA. The steps in the plan creation wizard will ask you to select the issue sources from JIRA,…

Hey Dwight, Great question. Sprints calculated in Portfolio will always start from the point of calculation. If you want to set fixed dates for your sprint I recommend you create a sprint on your agile board. You'll need to be using the board as an issue source in your plan and a team will need to be associated to that…

Hey Jade, I've upvoted your question so you should now have sufficient points to comment as often as you'd like Apologies, I should have seen from your link that you are referring to our classic plans. Unfortunately progress calculations in classic plans only include items linked to JIRA tickets. If this is an important…

Hey Jade, Good question. When you create issues in Portfolio they are not yet created/linked in JIRA; they're uncommitted and only exist in Portfolio. Only when you actively commit them will they be created in JIRA. These uncommitted issues will still be included in all progress calculations and estimates of uncommitted…

Hey @Brandon Olmstead, The + icon is only visible when there are no children of the issue. As soon as there's at least 1 child issue the "+" turns into an expand ">". To add another story to the Epic hover your mouse in-line where you want it to be and a line will appear. i.e: image2017-1-4 14:56:32.png This also works if…

Hey Kyle, Firstly is the relevant board associated with a team in your plan? On the team tab make sure you have a team associated with your board as an issue source (via the drop-down under the team name).This will make sure that your sprint dates, sprint issue assignment and sprint names are recognised in your plan. This…

Hey Donald, This is correct. The velocity represents the average velocity of the board's past 5 sprints. So in Portfolio if two teams are associated to the same board then that average value will be the recommended velocity for both teams without breaking it down for each team. In this scenario you would need to calculate…

Hey @Jean Luchtenberg, That's a good point. This occurs when an issue is created in JIRA for an epic that has no issues. The story is created and ranked at the bottom of the JIRA backlog. Because that story is the epic's highest ranked child item the entire epic is moved to the bottom. We don't have a good answer for this…

Hey Erik, The rank from Portfolio should generally be represented on the JIRA board, however there are some differences in epic rank behaviour between Portfolio and JIRA which can cause epics to be inconsistent. This is because the rank of epics in JIRA are independent to the rank of stories whereas in Portfolio the rank…

Also. In your support ticket can you please include the entire exception for the error? Thanks

Hey Kåre, Thanks for bringing this to our attention. We're sad to hear that you're receiving these errors. Could you please create a support request so that our devs can investigate and track your issue? https://support.atlassian.com/servicedesk/customer/portal/28 Thank you, Rhys

Hey Rikki, Yes there are plan specific permissions but these need to be set from within the plan configuration. In the config go to Permissions and you'll be able to set permissions for who can view or who can edit the plan. Please let me know if this is still an issue for you. Kind regards, Rhys

Please see my new answer for an implementation update and a new workaround guide. Feel free to add your feedback. Cheers,

Hey all, Just want to keep you in the loop that we've prioritised this problem. While it'd be preferable to use a native solution, for the interim I've attached a workaround guide for anyone that considers the lack of this functionality as a major issue/blocker: . This is especially recommended for server customers since…

Hey Anders, Unfortunately we currently don’t have a solution for handling concurrent sprints from the same board. Now that parallel sprints are implemented in JIRA Software we intend to implement functionality to handle this but we don’t have a good answer yet. You’re correct that right now Portfolio just picks to first…

Hey Alex,There are a couple of likely causes for this* Firstly, this could be related to a bug we’re aware of with hidden fix version fields (JPO-1283). You mentioned that you’re not using the releases feature so do you also happen to hide the Fix version/s field in your JIRA field configuration? If this is the case then…

Portfolio is still functional if you manage your plan using epics & initiatives without stories as long as the epics in your plan are allocated estimates that represent the child stories. Unfortunately if you don't source stories then the epics cannot aggregate the estimates from child stories. You'll need to assign the…

Hey Dante, The limit on the amount of issues you can load into your plan is 5000. However there is a hierarchy limit of 2000 which is the limit on the number of items that we are willing to render. So if your epics (+ initiatives if you use them) are < 2000 then we’re able to show you the epics level. If your Initiatives +…

Hey Paul, You're unable to assign multiple teams directly to the epic but you can assign multiple teams to its child stories which will then be represented on the Epic.

Hey Ashwin,You can only assign multiple teams to issues above the story level (i.e epic or higher). This is consistent with older versions of Portfolio where stories could only be assigned to one team.A story is generally a work item carried out by a single team. If a story is large enough to require multiple teams then…

Hi Oliver,The default value for releases in Portfolio is “Calculate”. Portfolio will attempt to schedule these issues into releases if there is capacity to complete these additional issues. If your releases do not have capacity for additional issues then issues with “Calculate” will be assigned to Later. Ideally we’d like…

Hey Roman, It is partly possible to link uncommitted issues to JIRA tickets depending on what your intended use case is. if you intend to create an association link (e.g relates to) between an uncommitted issue and an existing JIRA ticket then this isn’t possible. Uncommitted issues don’t actually exist as issues in JIRA…

Hey Tarun, The behaviour you describe isn't correct behaviour for Initiatives. Could you please provide additional information so we can determine why Initiatives are disappearing for you? Please explain how you've setup your initiatives and workflow. Does the "in-progress" status happen to be a "completed" status (i.e the…

Hey Peter, Apologies, I should've mentioned this feature isn't yet available on Cloud. Releases for cloud were held back during Summit. 2.1 is expected to be available for Cloud this week.