Hi, We started a project 3 months ago and have been, for the last month, trying to configure the latest version of Portfolio to work with our existing cloud JIRA boards. I have read conflicting reports suggesting that this is possible and that this isn't possible. From what we have seen, it's pretty much impossible to use on existing projects and works pretty well if you set up a new blank project and new portfolio at the same time, before any issues are added in. Has anyone else found this or are we doing something wrong?
Thanks for getting in touch. We just cannot seem to get anything to configure correctly when adding as existing project. So, we're currently in Sprint 6 of the project, so quite a bit of development has been done. We have an extensive backlog of items yet to play and can match these against our roadmap so we know when they should be played. Once we add the projects to Portfolio, it maps out the project based upon the capacity we have given it, however, it won't allow us to change sprint dates, or add a team of developers to more than 2 projects. Essentially, we have a dev team working across 15 microservices. Each micro service has it's own JIRA project (clients idea). Our teams are building a thin slice across all services and need to be attached to multiple projects. If I set up a blank instance it's fine, but it won't allow me to do this on the existing projects.
It sounds like you're explicitly hitting a limitation of the UI when you state the following –
If I set up a blank instance it's fine, but it won't allow me to do this on the existing projects.
Can you please use screenshots to show this problem to me? Sorry to prompt for more information but again, things seem to work as intended for me.
For instance, I can't do much to change Sprints that are already in-progress or planned when importing to Portfolio, but that seems intentional.
Here's a quick example, so no estimates have tracked through from Jira, all (pretty much) of the releases show 'later' despite the issues being linked to releases already in JIRA and the timeline is completely screwed up as it is showing our plan to run into December despite the info in JIRA only being mapped until the end of September (on this particular microservice)
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs