Vladimir P

Hi Walter Bellante 

We've posted a couple of times on the ‘indefinite’ schedule option as well as there are posts from others on this. 
We would like to know if this improvement is on your roadmap. We have invested time and moved almost all our dashbords to the new builder. However, we aren't making a permanent move to using them yet due to lack of the scheduling option without a time limit that is suitable for us, and which is available in the legacy builder. I've outlined the reasons in one of my previous posts. 

Can you share your plans/view on this? Thanks 

Big plus 1 to the ‘schedule indefinitely’ option AND the PDF formatting bugs. Please give these high priority 

Thanks Walter Bellante 

Is there any more insights you can share why the Indefinitely option isn't possible? 

Also, is there a way to send the ‘schedule expire’ alerts to more than one person? If the alert only can be sent to the person who created the schedule, then there is a risk of losing visibility on these alerts if the person, for example, leaves the team or business. Is there a workaround in getting visibility on the timing of DB schedules without manually checking each of them? 

Good news re PDF and PNG, thanks. 

hi Walter Bellante 

Thanks for the update re the new builder going to GA. 

We had a look and realised that the scheduling function has two key issues that prevents us to fully move to the new builder. 
 

1. The ‘Run for’ option has a time limit of 12 months max. Does that mean we manually have to check each DB and make sure it the scheduling period not ended? We have a lot of scheduled DBs to our partners and we can't have someone manually going checking all of them every year. There should be an option ‘Indefinitely’(as also someone mentioned that above)? 

2. Scheduled DB is only available in CSV and Excel. What about PDF? 99% of our uses case is PDF(and presumably fro oher customers).  This is another major blocker for us. 

Can you please let us know what is Zendesk's view on these items? 

Thanks for your response both. 

Walter Bellante tnoted your comment. We don't use Align to top or left much at it squeezes the reports together without a gap. Whereas, we do like to space them out a bit between themselves, and at the top so they are easier to consume. For that reason we use more the Place anywhere option, but it has a big issue when needing to move a report, which i described above. 

If Align on top or left would allow custom spacing(controlled by a user) it would be a good step forward, or if Place anywhere would allow moving reports easily that would be big. Tbh i don't understand why you need to free up space for repsots in Place anywhere, it should have the default behaviour the same as in the Align options IMO.  So maybe there should be a hybrid option between the Align and Place anywhere. And of course scrolling for all of them! 

Can't drag and drop a report if there isn't enough room for it. Eg., if I want to move a report in an existing DB from top to bottom, i can't do it for two reasons: 

a) the screen won't scroll down as you move the report

b) if there isn't enough 'free' space for the report to put into. I would need to move reports around to free up room for it first, and then I can only move it by a screen size step, drop the report, scroll down and then move the report, rinse & repeat. 

It feels it should be the following: 

- screen must scroll down as you move the report down 

- the space for the report opens up by pushing other reports down or to the side, depending what direction you move it in  

When I need to move a report in a multiple reports dashboard it becomes a daunting experience. This specific experience is better in the traditional builder imo 

Hi Walter Bellante 

I hope you are well. 

I'm hoping you could clarify if the dashboard schedule functionality to external users will be available with GA in Q4? 

This is a critical feature for us and we can't start using the new builder properly if it isn't available. This would also help us with planning of how much resource we need to dedicate to the migration. We have quite a few dashboards to move to the new builder, create bookmarks, schedule them etc. 

I can see in the plan above that this planned to be shipped in Q4, but I'd be grateful if you could clarify. 

Also, we have a few pieces of feedback re the new builder, what would be the best channel to share it via?

Hi Walter Bellante 

I hope you are well. 

I'm hoping you could clarify if the dashboard schedule functionality to external users will be available with GA in Q4? 

This is a critical feature for us and we can't start using the new builder properly if it isn't available. This would also help us with planning of how much resource we need to dedicate to the migration. We have quite a few dashboards to move to the new builder, create bookmarks, schedule them etc. 

I can see in the plan above that this planned to be shipped in Q4, but I'd be grateful if you could clarify. 

Also, we have a few pieces of feedback re the new builder, what would be the best channel to share it via? 

Hi there, 

Would some be able please to help to put an attribute together which would return me requester first comment in a table in Explore. 

There is a placeholder in Zendesk for it ticket.description however, there isn't an attribute or metric for it in Explore. We need that attribute(or metric)

Thanks a lot! 

Hi there, I'm not sure where is best to report bugs as I wasn't able to find anything on this in FAQ/Help site. 
 

1. In Explore the exclude tags feature doesn't work when using the Ticket tags attribute. Repo steps: 1. Add the ‘Ticket tags’ attribute to the report. 2. Attempt to Exclude a tag from the report. Isn't working for us. Only works when creating an attribute that exclude the tag via a formula. 

2. Changes made to reports via dashboard aren't captured straight in the dashboard. Have to publish, exit the DB, open again in order to see changes. Repo steps: Open an existing DB (old builder), click ‘Edit report’ in any report, make a change to the report, click Save to dashboard. The change isn't populated in the DB.