UI error when creating scheduled trigger if user account is restricted by what environments it can access

[matt.heinzelman]

Hello,

We are running version 2018.7.7 and have found an issue in the UI where we cannot create a scheduled trigger if a user account is restricted by what environments it can access. Here is the error we receive in the browser when trying to create the scheduled trigger:

Also, here is the full exception:

After looking at the error in the browser console, it looks like it’s failing to get the list of Environments for the “Source environment” dropdown.

For the Team that the user account is tied to, this is what Environments it’s restricted to:

If I remove all the Environments from the Team, the UI opens for the user to create the scheduled trigger. We would like to keep this Team restricted to those Environments, so for a workaround, we are having our administrators create the triggers.

If you have any questions, please let me know.

Thanks,

Matt Heinzelman
Automation & Installation Engineer

Cartegraph

[Kenneth_Bates]

Hi Matt,

Thanks for getting in touch! I’m terribly sorry you’re hitting this issue. We greatly appreciate you reporting this and providing that detailed information. I’ve been able to reproduce this behavior both in 2018.7.7 and in latest (2018.7.13) so unfortunately it’s still current. It looks like it’s a problem when the project’s lifecycle includes any environment in which the user doesn’t have access to. I’ve raised this as a bug and you can track its progress here.

Issue: TypeError on Scheduled Triggers if user doesn't have access to all environments for project

I’m sorry again about the inconvenience this has caused. Please don’t hesitate to reach out if you have any further questions or concerns moving forward.

Best regards,

Kenny

[matt.heinzelman]

Thanks for the update, Kenny! We will be looking forward to a fix for this issue in the future.

Thanks,
Matt

[Kenneth_Bates]

Hi Matt,

You’re very welcome! Please let us know if we can assist with anything moving forward.

Best regards,

Kenny