Alina Wright
Product Manager for Roles and Permissions
-
총 활동 수117
-
마지막 활동
-
회원 가입일
-
내가 팔로우하는 사용자 수0명
-
나를 팔로우하는 사용자 수5명
-
투표 수1
-
플랜 수45
활동 개요
Alina Wright님의 최근 활동-
Alina Wright님이 에 댓글을 입력함
Hi all, this is a key piece of feedback that we will consider for our multi brand efforts planned for later this year. I'll follow up on this post with updates, so please 'follow'.
-
Alina Wright님이 에 댓글을 입력함
공식 댓글 Hi everyone, have some good news for you. This is something we're planning on starting on this year. If you have a strong opinion on how you'd like to see this function, keep an eye out on this pos...
-
Alina Wright님이 에 댓글을 입력함
공식 댓글 Correct. This has been launched.
-
Alina Wright님이 에 댓글을 입력함
Sydney Neubauer and Kate - quick update! This has been fixed (permission to redact side conversations) has been coupled with the redact permission and documentation has been updated.
-
Alina Wright님이 에 댓글을 입력함
Hey Sydney Neubauer and Kate - thanks for bringing this to our attention. We've picked this up and are working on it. I don't have a timeline to share but we'll be moving the ability to redact in s...
-
Alina Wright님이 에 댓글을 입력함
Óskar Ómarsson - Keep an eye out for an announcement in April :)
-
Alina Wright님이 에 댓글을 입력함
Hey Krista Zaloudek - this is actually very timely feedback around something we're in the process of exploring now. Is it ok to reach out to you via email to schedule a user interview session?
-
Alina Wright님이 에 댓글을 입력함
Jamie Noell - for 3 (Granting all ticket access to be able to see the Suspended view is nearly impossible now with private groups), we're currently looking into solving this. I'm the PM for private...
-
Alina Wright님이 에 댓글을 입력함
Bram Kolk - can you share more about why you'd want to do that? What is the use case? I ask because we're looking into brand based access and I want to learn more about how you're using brands toda...
-
Alina Wright님이 에 댓글을 입력함
공식 댓글 Hey all, thanks for the continued feedback on this. Our plan is to delve into this suspended ticket view this year. It's a complicated problem with a not-so-straightforward solution on the backend ...