Board Not Giving The Same Options as a Software Project

[Jason Lucken]

I have a few Software Projects that are linked to one board. When I am using the consolidated board, I do not get options such as Issues, Components, Code, Releases, Project pages, or even the Insights button. If I add an app, it doesn't appear on the consolidated board but will on the software projects. 

How can I have my consolidated board give me all of the options a software project board gives me? 

[John Funk]

Hi Jason,

A board can only be linked directly back to a single project using the Location field. That's what determines what information is seen in the left hand side. So if you are using a board with a filter that includes multiple projects, you will never be able to directly see the details of each project on the left hand side. 

[John Funk]

Actually our approach is to use multiple issue types based on the work being done. However, that is mostly for metrics since not all work is the same type of work nor takes the same amount of time to do. 

[Trudy Claspill]

You will not be able to get Components and Releases to display in a board that consolidates issues from multiple projects. Those lists are project-specific, and there is no functionality in Jira that will consolidate those lists and provide you a way to view them like you do for a single project.

[Jason Lucken]

My hunch is rather than having multiple projects, I would need one project with multiple issue types to achieve my goal. Thoughts?  

[Trudy Claspill]

In my experience, Projects are aligned to either products being developed or to development teams. 

I tend to discourage different issue types, beyond the ones already available, without first understanding the problem trying to be solved by introducing more issue types.

I would need to know more about how and why you have organized your work as you currently have it to be able to provide informed feedback.

[Jason Lucken]

I am new to Agile, Scum, and working off a board that has been in use prior to my arrival. We have a small development group who's focus is on different area's but are not exclusive to a single area. A developer can have a story in multiple boards so we use a consolidated board for our scum activities but am finding I must not be getting the most of what Jira has to offer but again, I am still pretty green.    

[Trudy Claspill]

How is having separate projects/boards useful? What are the pros of having that setup? How would having everybody in one project negatively impact the teams/process?

What is useful about having a consolidated board? Why do you need the consolidated board to show the Components, Releases and other functionality?

If you can provide information about why your organization likes the current set up, and why you need the functionality not available in the current set up, I might be able to provide better feedback. There are many ways to solve data organization, visibility, and reporting challenges in Jira, but we need to better understand how the current set up of separate projects is being used and why that set up is useful.

[Jason Lucken]

The reason I asked about seeing the Components, Releases and other functionality is because some Apps that I would like to try out and the Insights button does not appear on the consolidated board which I would like to have. 

Since I did not setup any of the projects or boards, I am discovering there could be a better or proper way to have had these setup but I am asking some of the same questions you are.