Report doesn't show correct navigation panel

We've created a JIRA plug in for the cloud and installed it into our cloud environment.  When we go to other reports for our project, the navigation to the left looks like this:

other_reports.PNG

When we go to our report, the navigation looks like this:

our_report.png

Here's what our plug-in looks like:

{
    "name": "Our JIRA Plugin",
    "description": "Improve your risk management through state-of-the-art forecasting and machine learning for Agile projects.",
    "key": "com.us.plugin",
    "baseUrl": "https://www.ourserver.com/",
    "vendor": {
        "name": "Aptage",
        "url": "https://www.ourserver.com"
    },
    "authentication": {
        "type": "jwt"
    },
    "lifecycle": {
        "installed": "api/jira/add-on-installed-callback"
    },
    "apiVersion": 1,
    "links": {
        "self": "https://www.ourserver.com/api/jira/atlassian-connect.json",
        "documentation": "https://get.ourdoc.com/rbd/"
    },
    "modules": {
        "jiraReports": [
            {
                "url": "/risk-burndown?projectKey={project.key}",
                "description": {
                  "value": "Improve your risk management through state-of-the-art forecasting and machine learning for Agile projects."
                },
                "reportCategory": "forecast_management",
                "thumbnailUrl": "https://get.ourdoc.com/wp-content/uploads/2017/10/RBD-Graphic.jpg",
                "name": {
                    "value": "Us"
                },
                "key": "our-report"
            }
        ],
        "postInstallPage": {
            "url": "/risk-burndown",
            "name": {
                "value": "Login to Authorize",
                "i18n": "mypostinstallpage.name"
            },
            "key": "post-install"
        }
    },
    "scopes": [
        "read",
        "write"
    ]
}

Any suggestions on what we might be doing wrong?

 

2 answers

1 accepted

0 vote

Just wanted to update this thread.  In the support ticket we found there was actually a new bug in regards to the way the project key URL parameter was being used.  This bug appears to have been already fixed for our Cloud instances at this time and in turn I believe that this issue has now been resolved.

Thanks to @Walter Bodwell for reporting this problem to us.

0 vote

Hi @Walter Bodwell,

We are interested to help here if we can, but we might need to gather some private information in regards to this plugin or your site to be better able to help here.  As such I created a support request on your behalf over at https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-357898

If you could update this with the information I requested there, this should help us to progress this issue.

Cheers,

Andy

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Apr 10, 2018 in Marketplace Apps

Learn about how Stefan K. built one of the *first ever* Marketplace apps

In this post you will discover more about the evolution of K15t software, some big topics they're currently focusing on in the app space, and a rare (not not funny!) photo of founders Mike Cannon-Bro...

12,842 views 11 24
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you