Slow performance

[Mohamed Kadi]

I really like using the discovery board and all its features, but my god is it slow. All screens take a lot of time to load, every click I do takes a lot of time to load. It's close to being unworkable actually.

Adding a fast comment to an idea after I learned something? Nope, takes 15 seconds before I get to the right screen to add the comment. We have about 450 ideas and some custom fields, nothing too heavy I would think.

Does anyone else encounter this? Is there something I should take into account?

[Chris Timms · Accepted solution]

Hello @Simone Longoni ,

The date field structure JPD uses isn't well supported in the rest of Jira yet and I have found JQL has quite a bit of difficulty with it.

But, you can do what you are looking for in JPD directly!

• Set up a new view
• Add a new filter for Target Date
  • Date Starts within the next months
  • Enter a number for how far you want to look. e.g. entering 3 today will return all issues with a target date starting in January

This will show you all the ideas in your JPD project that start in the next three months. You can add additional filters (for example, if you want to only look at items that are in your backlog and not in flight).

Hope that helps!

Regards,

- C

[Simone Longoni]

Thanks @Chris Timms!

I am unfortunately looking for a way to send push notifications by email based on filter match.

Still, having a JPD view could enable a pull way to keep an eye on what is about to "expire".

Cheers,

Simone

[Tanguy Crusson]

Hi, you can use formatting on the date field to highlight the ideas for which a date is coming soon or overdue, then use that fields in your views:

[Bill Sheboy]

Hi @Simone Longoni 

You are correct, and...

After some digging and experimenting I found that the JPD team appears to have created a new "date range format", which is neither a date field nor JSON compatible.  Which is probably one reason it does not work with JQL or directly with automation rules.  (Although that second one can be hacked a bit using text functions and advanced edits...)

The format is plain text, like this {"start":"2023-11-13","end":"2023-12-13"}

I recommend regularly searching this group for "date field" to learn if the team has made any changes / improvements in using this field.  Otherwise, the suggestion Chris made seems to help with your Target Date checks.

Kind regards,
Bill

[Bill Sheboy]

Just a follow-up...

Based on your other responses that you want to do a "push" message, I believe you could using an automation rule:

• gather ideas with a non-empty date field using a lookup issues action and JQL
• parse the field to get the date value and perform a comparison with smart value, list filtering to your target {{now.minusDays(30).jiraDate}}
• and report out the results in a "push", such as email or message