nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can the Overview be imported to another project? I.e. product discovery project to Scrum Board?

Hannah Garvin

Reading some of the information about 'Insights' not being able to be imported from Project Discovery board to another board, can you advise if this is the same for the Overview section of an Idea when Idea tickets are imported into another project, like a scrum board please?

We previously thought the 'Overview' section of an Idea's ticket in a Project Discovery Board was imported to a Scrum Board, but recent use has seen this field not come across into the scrum board - this is having a big impact on our scrum boards and the quick access to the detailed information for a task/story/bug.....we note that moving tickets from a scrum board into a project discovery board takes the description and puts it into the 'Overview' section of the Ideas ticket but not the other way round.

The Project Discovery board is brilliant and makes for a great way to collaborate with our clients. However, we need things like Story points, and original estimates (Epics, labels) to be standard fields transferrable between the project discovery and scrum boards (and vice versa). Furthermore, if the project discovery boards also had the ability to 'price up' a project (assign an hrly rate and calculate cost of tickets and overall project), then this would remove the need for yet another spreadsheet/tool.

When Atalssian can offer the power of these functions as tools within the discovery board, it will allow us to remove the need to use other third-party apps or spreadsheets

Would really appreciate an update on the Overview detail and whether it is a bug preventing this information from being pulled across into a delivery ticket on a scrum board or if this integration just hasn't been built yet and if the latter, what is the future scope for this critical feature?

Accepted answers

All comments

Rohan Swami

Hi Hannah,

Thanks for your feedback here. There isn't a bug here, we deliberately chose not to pull the Overview into Jira Software boards because customers wanted to display different information in the discovery context of Jira Product Discovery vs the delivery context of Jira Software. What's the benefit you'll get from having the Jira Product Discovery fields appearing in Jira Software?

It's not in our roadmap (for now) to make improvements to the integration between Jira Software and Jira Product Discovery, we're currently prioritising sharing roadmaps to your internal stakeholders, full implementation of the creator/contributor roles and a whole host of reliability features we need in place for GA.

Hannah Garvin

We use the Project Discovery boards to create a backlog of work with our clients and scope out the approach and acceptance criteria in the Overview section with our developers. Therefore there is a massive benefit to us in being able to bring the overview text and attachments into the Scrum Board once client and devs sign off the Idea's ticket.

It seems odd that you wouldn't have the Overview as an integrated (even optional) import field into the Jira Scrum Board - it is absolutely integral to how we move Ideas into an agreed block of work.

Is this not something that would be a simple addition to the 'create delivery' ticket function in the project board?

We want to utilise all that Jira has on offer without having to introduce multiple third-party apps/spreadsheets - this really does seem like a fundamental piece of functionality - I appreciate what you are saying about the difference between what customers want to see v the delivery, but if this is meant to be a collaborative board for scoping out ideas, then there really should be an element that allows the project management team the ability to add Acceptance Criteria and Delivery approach to the Ideas ticket, that can then be imported into the Jira Scrum Board - without it, you have only considered the client frontend/front facing info and ignored the involvement developers play - thus causing silos and double working to get the ideas and full context/delivery approach into a scrum board.

I would ask you to reconsider your approach/focus here and at least determine the effort/cost of providing an option to import specific predefined fields into the scrum board from the project discovery board.

Rohan Swami

Thank you very much for that context, Hannah. For now I would suggest that you set up Automation rules to copy across data from Jira Product Discovery to linked Jira Software issues.

The Delivery tab is V1 of our JPD/JSW integration, we'll keep making improvements to it over time but we need to make some tough prioritisation decisions across the product, as I'm sure you can appreciate.

Hannah Garvin

Thanks @Rohan Swami are you able to provide any info on the Automation rules so we can look to set this up, please?

eraymond

Hi Rohan or other admins,

I'm trying to do the same thing using automation rules. I'd like to be able to copy the JPD Overview section into a Jira Software board, specifically the description field of the newly created delivery ticket. How would I go about doing that? Or if I can't get the overview, I'd at least like to be able to copy the description over. When I built an automation rule to copy over the description, nothing came over.

Rohan Swami

@eraymond most likely there's a bug with the Automation you've set up. Here's the Automation guide and here's the demo video for this. If you're still running into problems, please create a support ticket by selecting 'Give feedback' at the bottom of the left-nav in Jira Product Discovery.