Agreed. In the current UI, the text often runs together or is hard to parse. This is especially true for the descriptive text field, since it's just plain text with no other UI element. Descriptive text is often used for important notes and warnings, but users are unlikely to notice them without for...

Our team would definitely use a custom field that allows tables. I can imagine that would be useful for a variety of industries. For our application, the marketing team sometimes wants to display information in an email or web page via a table. This keeps information clear and reduces display proble...

I had no idea that existed, thank you! That was exactly what I needed

For visibility within teams, we create custom reports for a worker's tasks. This is a task-based report that displays all tasks from active projects assigned to that worker. However, we've found that on the few times we accidentally assign to a role AS WELL AS a worker, that task doesn't show up in ...

Well, folks, we have an answer! Directly from support: "I have confirmed directly with our Product team that what you’re experiencing is actually expected behavior with the new license model. Contributors (similar to the old Requestor role) can only view companies they’re assigned to, based on their...

I'll submit a ticket today. I think it's likely a bug, but I'll update the post when I hear back.

Agreed. This is really throwing a wrench in our license management. If we have to build a workaround for typeahead fields, it would require a lot of extra time to recreate a feature that already exists. 

Yes, the only option selected in that section is disabling the AI assistant

My company uses a typeahead field on most of our templates to indicate which client a project is for. The typeahead references our list of Companies. With the Light license, our main users were able to see all companies in this field. I was hoping to move some of them to the Contributor license and ...

Agreed. Something similar to the "This field is required" alert would make users aware of character limits. I'll also add, there should be an error that would prevent users from submitting issues when a field is over the character limit.