Issue while adding Filters Menu Gadget to a Dashboard

[Deleted user]

While adding gadget Filters Menu Gadget to our dash board, we get error that 'A license key is required for this plugin to work. Please get your JIRA Admin to enter the license key'

Could someone help on this?

Thanks

[Petter Gonçalves]

Hello Ramesh,

Please, confirm if this is the Gadget you are talking about:

- Menu Gadget for JIRA Server

If this is the gadget you are trying to use, I checked that it is provided by JIRA Service desk application, so you must be licensed with JSD to use it. otherwise, you will receive the error that you must have A license key to make it work.

Do you currently use JIRA Service Desk in your JIRA? If yes, you can navigate to User management > Product Access > Add yourself to the groups related to JIRA Service Desk application. Of course, you will occupy one seat of your SD license.

P.S: The actions above require global administration access. If you are not an Admin, request your Administrator to perform the steps for you.

Let me know if it answers your question.

[Deleted user]

Hi @Petter Gonçalves

Thanks for your reply

I have a service desk agent license and also I am Jira admin

When I open the dashboard I don't see any error, However it is blank.

However the user reported with below error is also having a service desk license

What could be the issue?

Thanks

[Petter Gonçalves]

Hello Ramesh,

Can you confirm if the plugin related to the gadget is properly installed in your Server? Have you tried to remove and add it back?

This is a free App, so I don't believe this problem is related to a license error once you have a license on JIRA SD.

If you are still facing this problem, I would recommend you to open a ticket with Atlassian standard support for further investigation:

- https://support.atlassian.com/contact/

Let us know their answer about this.

[Deleted user]

Hi @Petter Gonçalves

The Menu gadget in our jira shows Not DC approved -Update Requested

Does that mean we need to wait for the DC approved update to resolve this issue?

Thanks