Hi Community,
Reaching out for some help!
We have linked a Serviceproject to a Softwareproject, so that we can arrange our issues into epics and sprints.
But unfortunately on the Softwareproject the Roadmap isn't showing. I've read something about the filter settings. So I tried to change those, but then our tickets from the Serviceproject aren't visible on the Softwareproject.
Hopefully you can help me with some step-to-step instructions to make the Roadmap tab visible.
Thank you in advance! Br, Willie
Hello @Willie Lagraauw
Welcome to the community.
Are you using a Standard plan or a Premium plan for your Jira environment?
With Standard plans, Roadmaps can be created only for issues in one project. If your board filter does not constrain the board content to issues from only one project then you will not be able to create a roadmap.
If you need to include issues from multiple projects in your roadmap, you will have to upgrade to the Premium plan so you have access to Advanced Roadmaps. Or you will have to look at a third party app for creating roadmaps.
@Trudy Claspill thank you for your quick reply. We also want that the board filter only shows the issues from the service project that is connected. I only don't know how I can change the settings, because when I change the filter we can't see the issues from the service project any more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Willie Lagraauw
Please clarify exactly what you mean by you "linked" your service project to a software project. What steps did you take to accomplish this, as there is no native functionality to "link" one project to another.
With regard to changing the filter for the board, please show us the filter used by the board when it IS showing the issues from the Service project and then show us what you change it to such that the board stops showing the issues from the Service project.
We need to see the actual syntax/JQL of the filter. In your original post you have shown us just the name of the filter. The JQL will be displayed farther down on the same screen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Trudy Claspill , via this instruction I've tried to create a Kanban board. As a project I linked the Service management board and according to the instructions I needed to select my personal space as location. I can see the Kanban board including the issues from the Service management board. My colleagues can see the board but it's shows private and they cannot see the content on the board. Do you know I can change this so that my colleagues also can see the backlog and board?
This is the information on the page where I can change the filter settings. But when I select another filter the issues from the Freia IT Servicedesk board aren't visible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Willie Lagraauw
Thank you for that screen image.
From that image I can see that your filter is selecting information from just one project.
When I mentioned that you might need to change your board filter, I was referring to editing the filter JQL shown above. That will not be necessary in this case because it is already set to select issues from only one project.
When the Location for a Board is set to your personal Profile, the Roadmap option will not be available. I have not yet found documentation that states this, but that is what my experimentation reveals.
My experimentation also reveals that even though the board filter picks issues from only one project (your service project), when you set the Location for the board to another project (a software project) then Jira interprets that as the board being configured for multiple projects and the Roadmap option will not work for you even if it is enabled.
There does not appear to be a method to create a board for a Service project and also get the Roadmap feature.
Can you tell us more about your scenario? If we understand your scenario better we may be able to offer alternative solutions.
- Why are you using a Service project to document issues instead of a Software project?
- Why do you want to organize the Service issues into Epics and Sprints?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks again for the explanation. I know understand why the roadmap isn't working on this board.
To come back on your questions:
- I really don't know why we use a Service project instead of a Software project. Probably got something to the with the end-users that can create tickets and those tickets are visible on the Service project. Don't know if this kind of functionalities will work with a Software project. The end-users don't have a Jira license.
- We want to get a better overview of the work load. Ofcourse we have bugs/incidents that needed to be solved asap, but we also get a lot of change requests. This request we want to organize in epics and sprints, so that we can plan a release and communicate to the end-users about the content of the release and what's is comming up next.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you need users to be able to create issues without a Jira Software license, then a Service project is the correct solution.
An alternative you can consider is making copies of the Service project issues into a Software project. Then you would be able to create a roadmap in the Software project for the copies of the issues in that project. You could use Automation rules to create the copies.
Your unlicensed end users would not be able to see the issues in the Software project.
If you need to keep your end users informed about changes to the Software issues, you could also automatically link the Software issues to the Service issues, and use automation to transfer information between those linked issues so that your end users could view the information in their Service Project issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.