Project page navigation doesn't work properly for some team managed projects

Forge
1

Hi,
We have submitted a new app for approval and find out that project page page navigation is not rendered if the project is a team managed project and using vertical navigation. This only happens for team managed projects which uses vertical navigation. If project’s navigation is rendered on the top, it works. Is there anything we can do about this?

image
image1259×1302 87.1 KB

1 Like
4

Hi @denizoguz thanks for asking!

At the moment the projects sidebar only works for company-managed projects, https://developer.atlassian.com/cloud/jira/platform/navigation/

Menu items in the navigation create entry points into your app. The navigation system includes extension points for the:

  • Top menu
  • Company-managed projects sidebar
  • Company-managed project settings
  • Jira settings
  • User profile menu

Extension points for team-managed projects are coming soon.

I’d say that’s why you’re running into this issue.

I’d recommend doing a check to see whether it’s a team-managed or company-managed project to prevent the app from rendering incorrectly in team-managed projects for the time being.

Hope this helps!
Mel

1 Like
5

Hi @mpaisley ,
Thanks for the answer. Yes, it is a team managed project. But it works for some team managed projects. It doesn’t work for some of them and it depends on how the project navigation is rendered (horizontal/vertical).

6

Hi,
Can you tell me a bit more about your app? Are you using the jira:projectPage module - and if so can you share your configuration for that module in your manifest?

I’ve created a simple page using

jira:projectPage:
    - key: learntoforge-project-page
      function: project-sidenav
      title: Learn Forge (Module Jira Project Page)

and

import ForgeUI, { ProjectPage, render, Text } from "@forge/ui";

const App = () => {
    return (
        <ProjectPage>
            <Text>Hello, world!</Text>
        </ProjectPage>
    );
};
export const run = render(<App />);

and it is rendering vertically in both Team and Company managed projects (contrary to what the documentation states).

Screen Shot 2023-04-05 at 3.08.15 pm
Screen Shot 2023-04-05 at 3.08.15 pm1880×2408 196 KB

I’d like to understand how to reproduce what you’re seeing.

1 Like
7

Hi,
You have to add multiple sections or pages, so that Forge will try to render it as a collapsable section. Error occurs when you expand it. Instead of listing all defined sections/pages, it renders a corrupt UI. Actually I have created a bug report for it, no one triaged it yet. Forge - Issues - Ecosystem Jira

  1. Create a new forge project using “jira-project-settings-page-custom-ui” template
  2. Update “projectSettingsPage" section as follows to add routes:
jira:projectSettingsPage:
    - key: testps-hello-world-page
      resource: main
      resolver:
        function: resolver
      title: TestPS
      sections:
        - pages:
            - title: Page 1
              route: /page1
            - title: Page 2
              route: /page2
        - header: " "
          pages:
            - title: Help
              route: /help
8

Hi @denizoguz are you using UI Kit or Custom UI?

9

Hi,
CustomUI. But, you don’t need to add any app logic. Just adding subpages to manifest.yml is enough to reproduce this issue. So, It should also happen when using UIkit.

10

OK thanks, I’ve replicated it now un CustomUI - so it works for business projects regardless of whether they’re team or company managed as they are horizontal but for software projects which are vertical there are problems for team managed projects but not company managed.
I’m still trying to determine whether this is due to this functionality not being implemented for team managed projects - leave it with me. I’ll update you soon.

1 Like
12

Hey @denizoguz, sorry I didn’t provide an update at the end of last week - I’m in a different timezone to the team working on this part of Forge and we’ve all just had a long weekend for Easter. They have confirmed the problem and worked out that the cause is actually not related to the module itself and will investigate a fix this week.
Cheers!
Melissa

2 Likes