Not able to see issues from team-managed projects in the company-managed project

[José Carlos De Oliveira Escalona]

Hi, I got a company-managed board that suppose to catch issues from all my team-managed projects

The filters includes 2 projects, however, is not including issues from this project, only from the Service Desk one

How can I visualise the issues from all these other projects so I can have a big concise Sprint?

[Trudy Claspill · Accepted solution]

Hello @José Carlos De Oliveira Escalona 

Are the statuses used in the SFDC issues mapped to columns in this multiple project board? Can you show us the Columns mapping for this board?

[José Carlos De Oliveira Escalona]

Thanks for your reply Trudy, I was not aware of that!

I have now mapped them and I can see nearly* all issues.

*I just missing the issue types from the Jira Discovery Project

[Trudy Claspill]

Hello @José Carlos De Oliveira Escalona 

I have not worked with Product Discovery at all, so I don't have an answer for that.

Since that was not mentioned in your post originally, I recommend that you start a new Question about showing Product Discovery information within a Jira Software Company Managed project.

Also, there is a Community Group specifically for Product Discovery. You might want to check that out and join it, if you have not done so already.

https://community.atlassian.com/t5/Jira-Product-Discovery/gh-p/jira-product-discovery

[Bill Sheboy]

Hi @José Carlos De Oliveira Escalona 

What problem are you trying to solve by adding ideas from a Jira Product Discovery (JPD) project to another board?

Putting JPD ideas on another board seems to invert the concept and value of using JPD, which is to perform highest level, portfolio management and planning.  Often a JPD project is the source of the ideas which then lead to work items (i.e., Epics, Stories, etc.) on other Jira project boards.

Kind regards,
Bill

[José Carlos De Oliveira Escalona]

Hi @Bill Sheboy 

Thanks for your comment and absolutely....I agree with you the development work should emerge from Ideas.

The issue is I am solo database administrator, so I need wear different hats in my role:

- As a BA, I will need to carryout discovery sessions, develop Ideas, generate requirements from those ideas, validate etc etc

- As a developer, I will need to take those requirements and convert them into delivarables and tangible items to deploy

- As a Project Manager, I need a place to monitor all the projects in a High Level view where I can log updates and discuss with stakeholders

- As Database Administrator, I will need to work in the cases from the Service Desk and correct issues, sometime create new requirements from there.

To manage all this, I was looking for a single place as a unique source of truth.

So having a unified board, I can have any work item I can do in a Sprint, that means any...it could be an idea to develop investigating the current state, meetings with stakeholders to generate requirements for a further sprint....and the next item could be developing and deploying a requirement caught previously...

As you can see, I am using a range of tools to achieve this (Atlas, Service, Discovery, Software, Confluence)!

I hope it makes sense but I am really open to ideas of how I can handle this better :-) !

[Bill Sheboy]

Thanks for explaining the situation, and I expect you will not find a "one size fits all" answer.

The different things you note require different capabilities / Jira features.  If there was a simple way to roll those up together, Jira would already provide it.  For example, if there was a single board to show JPD Ideas and their development Epics and perhaps even Stories mapped to the Epics...that would need to be read-only.  Otherwise changing one of those (out of the context of their board / view) would break things for others.

You could try creating a dashboard with multiple Filter Results gadgets, showing the different areas, but again that would be read-only.